{-- Thu, 25 Apr 2013 11:46:23 -0400: Enoch wrote: --}
Enoch> Your amforth-shell.py is designed for importing and that's a good
Enoch> starting point. I am sure that we can copy ideas from the various
python
Enoch> development approaches under emacs to modify gforth.el. All that we
need
Keith Amidon writes:
> {-- Tue, 23 Apr 2013 12:12:50 -0400: Enoch wrote: --}
>
> Enoch> Specialized IDEs are great but for me it's Emacs for
> Enoch> everything.
>
> It's emacs for everything for me as well. Take a look at the mail user
> agent this email comes from... ;-)
>
> Enoch> I
{-- Tue, 23 Apr 2013 12:12:50 -0400: Enoch wrote: --}
Enoch> Specialized IDEs are great but for me it's Emacs for
Enoch> everything.
It's emacs for everything for me as well. Take a look at the mail user
agent this email comes from... ;-)
Enoch> I am using (a customized version of) gfo
m/holon/papers/ef95.htm
>
>
>
>
> De: Rafael Gonzalez
> Para: Everything around amforth
> Enviado: Martes 23 de abril de 2013 12:01
> Asunto: Re: [Amforth] amforth-shell.py bugfix
>
>
>
> I think the python script is becoming more and more
23 de abril de 2013 12:01
Asunto: Re: [Amforth] amforth-shell.py bugfix
I think the python script is becoming more and more complex.
Maybe it is the time to switch to an umbilical-like system.
For that, a new tool is needed and HolonU may be what your are looking for.
http
Enviado: Sábado 20 de abril de 2013 9:30
Asunto: Re: [Amforth] amforth-shell.py bugfix
Hi Hannu,
> Take words and see them all. Produce dot file and make callgraph or
> wordgraph. Anyway to see what gets used where and in which order.
Crazy. I think, a real forth interpreter with a modifie
Hi Hannu,
> Take words and see them all. Produce dot file and make callgraph or
> wordgraph. Anyway to see what gets used where and in which order.
Crazy. I think, a real forth interpreter with a modified code generator
(like the debugger in amforth) would be easier to use than a python
based heu
> To: amforth-devel@lists.sourceforge.net
> From: i...@hotmail.com
> Date: Fri, 19 Apr 2013 18:51:09 -0400
> Subject: Re: [Amforth] amforth-shell.py bugfix
> I have two more developments planned for the shell, one easy -- one
> tough... The tough one I mentioned already, which
Matthias Trute writes:
> Hi,
>
>> I added an #include-once directive and let it default to "no" (current
>> behavior). Also added was a program argument to change the default
>> behavior if one so desires [me]. Testing done as well.
>>
>> http://pastebin.com/5Mfrvzdw
>
> Applied. And Thanks to
Hi,
> I added an #include-once directive and let it default to "no" (current
> behavior). Also added was a program argument to change the default
> behavior if one so desires [me]. Testing done as well.
>
> http://pastebin.com/5Mfrvzdw
Applied. And Thanks to Keith for discussion.
btw: I agree
I added an #include-once directive and let it default to "no" (current
behavior). Also added was a program argument to change the default
behavior if one so desires [me]. Testing done as well.
http://pastebin.com/5Mfrvzdw
Regards, Enoch.
Keith Amidon writes:
> {-- Mon, 15 Apr 2013 12:52:45
{-- Mon, 15 Apr 2013 12:52:45 -0400: Enoch wrote: --}
Enoch> As this is our first direct communication, thank you for contributing
Enoch> the shell.
Thanks for your appreciation. I've really enjoyed working on my amforth
projects and just wish I had more time for them. ;-)
Enoch> I did r
Hi Keith,
As this is our first direct communication, thank you for contributing
the shell.
Keith Amidon writes:
> {-- Mon, 15 Apr 2013 03:03:55 -0400: Enoch wrote: --}
>
> Enoch> Hello Matthias & All:
> Enoch> amforth-shell.py bugfix. skips already uploaded #include files.
>
> Enoch> htt
Matthias Trute writes:
>> amforth-shell.py bugfix. skips already uploaded #include files.
>
> This would break my standard workflow:
> start shell
> do
> flash controller
> upload files with #include (via cursor up-history)
> test
> again
Hello Matthias,
I guess you better alter the above
{-- Mon, 15 Apr 2013 03:03:55 -0400: Enoch wrote: --}
Enoch> Hello Matthias & All:
Enoch> amforth-shell.py bugfix. skips already uploaded #include files.
Enoch> http://pastebin.com/ePa76LmL
I can see how this would be useful in some circumstances. However, in
interactive development I up
Hi Enoch,
> Hello Matthias & All:
>
> amforth-shell.py bugfix. skips already uploaded #include files.
This would break my standard workflow:
start shell
do
flash controller
upload files with #include (via cursor up-history)
test
again
I would prefer something like
require as specified
i
Hello Matthias & All:
amforth-shell.py bugfix. skips already uploaded #include files.
http://pastebin.com/ePa76LmL
Regards, Enoch.
--
Precog is a next-generation analytics platform capable of advanced
analytics on semi
17 matches
Mail list logo
