Hi, Thanks, verified, works for me now.
Juergen Sauermann <juergen.sauerm...@t-online.de> writes: > Hi, > > fixed in *SVN 897.* > > /// Jürgen > > > On 02/25/2017 05:31 PM, Alexey Veretennikov wrote: >> Hi, >> >> Doesn't seem to work: >> My lib0 is >> /Users/alexeyv/Sources/apl/gapl-workspaces/workspaces/CONTINUE >> >> CONTINUE file is removed. >> The SETUP.apl is in the same directory. >> >> On attempt to run APL I get: >> ================ >> )LOAD CONTINUE (file >> /Users/alexeyv/Sources/apl/gapl-workspaces/workspaces/CONTINUE) failed: No >> such file or directory >> ================ >> >> and the SETUP.apl is not loaded. >> >> >> Alexey Veretennikov <alexey.veretenni...@gmail.com> writes: >> >>> Thanks! >>> >>> I'll try it out. >>> >>> One question though: why is this so strange syntax for user commands? >>> Why not to have say in monadic usage the argument as an array and with >>> the command itself stripped? It would allow to make easier user commands. >>> >>> Juergen Sauermann <juergen.sauerm...@t-online.de> writes: >>> >>>> Hi, >>>> >>>> regarding user defined commands I have changed the following in SVN 896: >>>> >>>> 1. )CLEAR also clears all user defined commands >>>> >>>> 2. )SAVE and )DUMP also save user defined commands so that they >>>> are available after )LOADing the workspace again. >>>> >>>> 3. If a workspace named SETUP (either .apl or .xml) exists in )LIB 0 then >>>> it is )LOADed automatically unless a CONTINUE workspace exists as >>>> well. The SETUP workspace can be used, for example, to set up user >>>> defined commands that shall exist in all workspaces. >>>> >>>> 4. For older workspaces, you can )COPY the SETUP workspace. However, >>>> this only works for )DUMPed workspaces (i.e. .apl files). >>>> >>>> Elias, this change has moved the user defined commands from class Command >>>> to class Workspace. If have updated the emacs code accordingly; please >>>> sync back. >>>> >>>> /// Jürgen >>>> >>>> > -- Br, /Alexey
