Re: [Bug-apl] emacs and apl

[enztec]

I did take a look and the horrors of the 12th Emacs Vim Battle at GNU Harbour 
came back in a flash and shut that down ;)
http://en.wikipedia.org/wiki/Editor_war

I wonder if editing the function in the ws.xml file and then reloading might be 
an avenue to explore?



On Fri, 25 Apr 2014 12:37:03 +0800
Elias Mårtenson wrote:

> When it comes to things like development environment integration (things
> like SLIME for Common Lisp as well as the gnu-apl-mode) Emacs is clearly
> the better choice, Why not take a look at Emacs? You might actually like
> it. :-)
> 
> Regards,
> Elias
> 
> 
> On 25 April 2014 09:36, enztec wrote:
> 
> >
> > Nothing like that - more like i've always been active in the emacs vs vim
> > wars and it would be hypocritical to start using emacs now!!
> >
> > I remember using ∇ exclusively with tcc apl ()edit with stsc) and can't
> > find how to get a line open for editing and the cursor positioned on the
> > line
> > I keep trying (something from my memory)  ∇fns[1⎕4] to position the curson
> > at char 4 on line 1 but it all it does is display lines 1 to 4 and then
> > open line [5] for input
> >
> >
> >
> > On Fri, 25 Apr 2014 09:11:51 +0800
> > Elias Mårtenson wrote:
> >
> > > Totally specific to Emacs. The entire module is written in Emacs Lisp.
> > That
> > > said, you can run Emacs in a terminal if you are allergic to graphical
> > > displays. :-)
> > >
> > > Regards,
> > > Elias
> > > On 25 Apr 2014 09:06, <enztec> wrote:
> > >
> > > > Hi
> > > >
> > > > It is something totally specific to emacs or is is something that
> > might be
> > > > usable in an xterm?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Fri, 25 Apr 2014 08:58:33 +0800
> > > > Elias Mårtenson
> > > >
> > > > > It edits functions in the workspace. GNU APL runs inside Emacs, and
> > when
> > > > > you press C-c C-f to open a function it reads the content of it and
> > > > > displays it in a separate buffer. Once you're done editing it gets
> > sent
> > > > to
> > > > > the APL runtime.
> > > >
> > > > > >
> > > >
> > > >
> >
> >