From: Keith A. <ca...@pi...> - 2013-04-23 16:49:00
|
{-- Tue, 23 Apr 2013 12:12:50 -0400: Enoch <ix...@ho...> 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) gforth.el from the gforth Enoch> project. As we are all dreaming now... I hope to see Gforth Enoch> specifics replaced by AmForth specifics (sending code via Enoch> serial I/O rather to an inferior Gforth process). Time to wake Enoch> up now :-) I did briefly look at modifying the forth-mode code from gforth to work with amforth using amforth-shell.py to manage the interaction. In principle it shouldn't be terribly difficult to do but forth-mode seemed fairly gforth specific and I didn't want to spend the time to try and abstract it in addition to writing another backend. I haven't actually tried this but I think that a poor-man's version of emacs integration can be achieved by using shell-command-on-region, by default bound to "M-|", and the command "amforth-shell -p /dev/<tty>". This should send the region to amforth-shell as standard input which will be sent to the device. The output will be in a buffer named "*Shell Command Output*" which you can review to make sure the upload was successful. --- Keith |