Right now, the Emacs mode preprocesses all input being typed by the user,
and if he types ∇ followed by a symbol name, the external function editor
is opened and the command is never actually sent to the interpreter. This
works fairly well, but there are some annoyances:

   - Emacs doesn't know if the typed text is on the command line, or input
   from ⍞, for example.
   - There are some buffer state issues in Emacs that is caused by a
   newline being inserted which messes up the parsing of the prompt.

I think a better solution would be if there was a way I could ask GNU APL
to not start the internal line-based function editor, and instead reply
with some special code (prefixed by a special character perhaps?) that
could trigger the opening of the function editor.

Another solution could be to control this from the native code plugin. For
example a function that I could call to register a callback that is called
whenever the ∇fn command is issued.

All of the above also applied to the )ED command that I discussed in my
previous mail.

Regards,
Elias

Reply via email to