Dear Juergen,
The -f option works well for APL script files but it doesn't load
workspaces. Additionally, the -f option requires a path, )LOAD uses an
implied path.
I have a saved workspace named "Books.xml". I use it by starting APL from
anywhere and then typing ")Load Books". I want to be able to do:
apl -L Books
It should start APL and ")LOAD Books".
The -f option doesn't work with workspaces and it requires a path.
I now see that I can use the --LX option to do what I need, but I would
still prefer the cleaner -L option I suggest. So, this works:
apl --LX ')load Books'
but I'd still like to have the -L option to do something common in an
easier way.
Also, can you make "-q" a synonym for "--silent". This is what most
programs use.
This would be greatly appreciated! Thanks.
Blake
On Thu, Nov 13, 2014 at 5:11 AM, Juergen Sauermann <
[email protected]> wrote:
> Hi Blake,
>
> I can look into that. I guess I need a little more information, for example
> what the difference to *apl -f workspace* is.
>
> /// Jürgen
>
>
> On 11/13/2014 04:13 AM, Blake McBride wrote:
>
> Greetings,
>
> It would be nice if GNU APL had a command line argument to specify a
> workspace to autoload on startup (rather than CONTINUE). Here is the use
> case:
>
> I create an application in GNU APL. I want the user (who doesn't know
> programming) to simply click on something that starts the app. If I can
> cause GNU APL to load a specified WS, I can have different links start up
> different APL applications.
>
> When the user ends the app, I execute ⍎')off' thus the user never has to
> know anything about APL.
>
> Thanks.
>
> Blake
>
>
>
>
>
