Speaking of the Emacs mode. The latest version supports tab-expansion of user-defined commands. Thank Jürgen for providing me with the necessary information to make this possible.
Regards, Elias On 8 May 2014 00:19, David B. Lamkins <dlamk...@gmail.com> wrote: > I had to ponder this for a few moments, since I've become so accustomed > to working with APL scripts rather than workspaces. (Kudos to Elias for > gnu-apl-mode!) > > Of course it makes perfect sense that you wouldn't want to wipe out your > ]USERCMD definitions when (re) )LOADing a workspace from an xml file: > the workspace file can't (re-)establish the ]USERCMD definitions that it > needs. > > Fair enough... > > Turning to a script-based use case, then: > > When a script contains ]USERCMD definitions, re-)LOADing the script > reruns the ]USERCMD definitions. In this case, each redefinition causes > a (harmless, in this case) BAD COMMAND message. > > It'd be helpful if the BAD COMMAND message was suppressed in the case of > redefining a ]USERCMD identically to its existing definition. > > > On Wed, 2014-05-07 at 12:40 +0200, Juergen Sauermann wrote: > > Hi David, > > > > I think they should because commands work outside of workspaces. > > Think of one workspace installing commands and another using them. > > You can ]USERCMD REMOVE-ALL to remove all commands. > > > > /// Jürgen > > > > > > On 05/06/2014 09:41 PM, David Lamkins wrote: > > > > > Thank you. > > > > > > One more thing: ]usercmd definitions probably shouldn't survive > > > )load and )clear. > > > >
