> In the process of testing jfricas I tried to use the fricas script
> which I never use. I usually use directly FRICASsys.
You certainly know that calling "fricas -nosman" is equivalent to
calling FRICASsys directly, but with the right environment variables
(FRICAS) set.
> But to properly start FriCAS and not having an error message 'X cannot
> be found' I tried to use 'fricas' with the good option, i.e. just in a
> terminal here.
> Following is a result of a sample session:
> Unknown option: --nox
Come on, you should know that AXIOM was invented before they started the
convention that only single letter options should have just one dash.
It's "-nox" and not "--nox".
But be careful. If you want to use it in connection with jfricas, Kurt
realized that it will hang when you try to draw something. Honestly, I
haven't actually tested this situation.
And unfortuately, if you want to use "fricas -nosman" instead, that is
something that did not work on my computer. As you see in
fricaskernel.py, for me it worked with
pid = Popen(['gnome-terminal', '--title=jfricas', '--'] +
['fricas','-nosman','-eval',prereq,'-eval',start])
If it works on your side without putting the first list (gnome-terminal)
in front, I would be happy to learn about your setup.
> As a suggestion, what about adding '--help' option and eventually
> '--version' option?
Yes, I'll prepare a pull request for it. Or are you quicker?
> Additionally, I wonder why the error message is always:
>
> To use a specific workspace use, e.g.: fricas -ws YourWrongOption.
> Goodbye
I also don't know. Nobody has complained up to now. ;-)
> What about returning:
> Unrecognized option '********'
> Try 'fricas -h' or 'WhateverYouWant' for more information.
Right.
Ralf