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.
On May 6, 2014 10:57 AM, "Juergen Sauermann"
<juergen.sauerm...@t-online.de <mailto:juergen.sauerm...@t-online.de>>
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. 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\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 of
the escaped values.)
