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 wrote:
> I had to ponder this for a few moments, since I've b
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 fi
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 defi
Thank you.
One more thing: ]usercmd definitions probably shouldn't survive )load and
)clear.
On May 6, 2014 10:57 AM, "Juergen Sauermann"
wrote:
> Hi David.
>
> thanks. Removing first and printing then was maybe not so smart. SVN 251.
>
> /// Jürgen
>
>
> On 05/06/2014 06:47 PM, David B. Lamkin
Hi David.
thanks. Removing first and printing then was maybe not so smart. SVN 251.
/// Jürgen
On 05/06/2014 06:47 PM, David B. Lamkins wrote:
Thank you, Jürgen! That'll do what I need.
FYI, I'm seeing a bit of cruft on the REMOVE:
]usercmd remove ]foo
User-defined command \371\
There's also a bit of confusion in the handling of remove. In this case,
]pkg is a usercmd:
]usercmd remove ]foo
User-defined command ]pkg removed.
On Tue, 2014-05-06 at 17:07 +0200, Juergen Sauermann wrote:
> Hi David, Peter,
>
> I have added a simple facility for adding user defined
Thank you, Jürgen! That'll do what I need.
FYI, I'm seeing a bit of cruft on the REMOVE:
]usercmd remove ]foo
User-defined command \371\217\212\277\200
(Tested in both gnu-apl-mode [as above] and in a terminal. Only
difference is that the terminal shows unprintable `?' glyphs instead o
Hi Elias,
just loop around user_commands:
*loop(u, user_commands.size())
{
user_commands[u].prefix ... // the command
user_commands[u].apl_function ... // the APL function called
...
}*
in SVN 250 you have to add *public: *before the declaration of
user_commands
Right now I'm using the .def files to retrieve the list of ]-commands (for
tab-expansion). Clearly this will not be enough if there is a facility to
add new ones at runtime.
What method should I use to get a full list of these commands from within a
native function?
Regards,
Elias
On 6 May 2014
Hi David, Peter,
I have added a *simple* facility for adding user defined commands (the
command being
implemented in APL (possibly as native function)). I will no go as far
as described in Dyalog's document below, however.
This could also be used for experimental commands or commands "missing
On Sat, 2014-05-03 at 14:22 +0800, Elias Mårtenson wrote:
> As much as I am a fan of extensions, I have to admit that I don't
> fully understand the justification for this. After all, the
> pkg-commands are plain functions, so why not expose them as such?
The short answer is that some tasks seem m
On Sat, 2014-05-03 at 15:02 +0200, Juergen Sauermann wrote:
> Hi David,
>
> from what I hear Dyalog APL seems to be a good interpreter and I have no
> problem with it.
> I am only a little more conservative when it comes to new and
> non-standard APL features.
> But Peter Teeson had ideas going
Hi David,
from what I hear Dyalog APL seems to be a good interpreter and I have no
problem with it.
I am only a little more conservative when it comes to new and
non-standard APL features.
But Peter Teeson had ideas going into a similar direction.
One question that I have is how the implement
As much as I am a fan of extensions, I have to admit that I don't fully
understand the justification for this. After all, the pkg-commands are
plain functions, so why not expose them as such?
Regards,
Elias
On 3 May 2014 13:27, "David B. Lamkins" wrote:
> During a few idle moments at work today,
During a few idle moments at work today, I flipped through some of the
BAA archives and came across a short article regarding Dyalog's
extension to allow user-defined commands.
Yah, I know... Dyalog. But hear me out.
I've been thinking ahead to a time when I'll be ready to roll out the
package ma
15 matches
Mail list logo
