|
Hi again,
coming back to our earlier discussion, I have added a profile
facility to the
preferences file. You can say eg:
apl -p 2
and then only the lines without a profile and those following a
line saying
Profile 2
until the next such line are picked from the preferences files.
/// Jürgen
On 06/10/2014 05:55 PM, Elias Mårtenson wrote:
In the Android version that is a bit problematic
still. This is because I have no control over the directories
where I can save files. What I do is to construct a command line
dynamically and call the apl_init() (or was it init_apl()? I'm
on my phone now so I can't check) function with it.
Note that I don't necessarily even have a writable
home directory.
However, passing on the command line is of course not
the only way. You can have a global variable where I put the
information too.
Regards,
Elias
On 10 Jun 2014 17:38, "Juergen Sauermann"
< address@hidden>
wrote:
Hi,
I have added $HOME/.config/gnu-apl/preferences in SVN 317.
The files read are now:
1.
/etc/gnu-apl.d/preferences (or
/usr/local/etc/gnu-apl.d/preferences)
2. $HOME/.gnu-apl/preferences, and
3. $HOME/.config/gnu-apl/preferences (if
2.failed).
I believe that paths on the command line are rather
cumbersome.
A better approach could be profiles inside (or next to)
the preferences files.
You could then select a profile number on the command line
and the settings
of that profile (paths, colors, etc) will be used when GNU
APL is started.
/// Jürgen
On 06/05/2014 05:17 PM, Kacper Gutowski wrote:
On 2014-06-05 22:39:52, Elias Mårtenson wrote:
May I also ask that after reading the main config file, the interpreter also
reads $HOME/.gnu-apl.d for load user-level configuration. And finally, it
should also check the commandline so that the paths can be overridden on a
session-basis.
Doesn't it already read $HOME/.gnu-apl/ (without .d)? Though, I would prefer
this to be put under $HOME/.config/gnu-apl/ and to be configurable through
environment (in addition to command line arguments).
-k
|