On Aug 16, 12:14 pm, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> Imo, Leo 4.5 b4 should attempt to handle settings in a more standard
> manner.
Many thanks to all who have offered suggestions and comments. The
following post summarizes my present plans.
1. Everyone seems agree that the following structure for settings
files is good:
$HOME/.leo
leoID.txt
myLeoSettings.leo
etc..
2. (controversial?) There is a question of what to do about $HOME/
myLeoSettings.leo. I don't like either of the following suggestions:
QQQ
1) Leo tries to be smart and looks for both ~/[my]leoSettings.leo
and
~/.leo/[my]leoSettings.leo, uses which ever it finds and complains
very
loudly if it finds both.
2) Change the default behavior so it always looks in ~/.leo, but
for
some transitional period (a year or two?) check for them in ~ and
complain loudly telling the user to move them - force the user to
move
them by ignoring them and just explaining the problem. I.e. "I
found
you config file but I'm not using it because it's in the wrong
place".
QQQ
1) will just cause more confusion, and 2) just delays the "day of
transition" to a time when we've all forgotten the issues
involved :-) Imo, the thing to do is simply to make the transition
*now*, and get the pain over with. Leo can, without confusion, warn
that it is ignoring $HOME/.myLeoSettings.leo.
3. (controversial?) The present code creates myLeoSettings.leo if it
doesn't exist. I don't like it, and it has already created
installation problems. This should be an option, but it can't be an
option because creating myLeoSettings.leo happens too early.
So I'm going to take out this code. A create-my-leo-settings-leo
command might be helpful...
So much for configuration settings, per se.
Let us now consider the question of directories for Leo's shadow
files.
1. The suggestion was to change .leo_shadow to .leo/shadow. This may
be possible now::
@string shadow_subdir = .leo/shadow
I'll make sure Leo's code makes this possible.
2. Ville makes an important observation re Linux:
"as it is now, you require write access to the directory
where the files are. Not optimal for all situations..."
You could call this a problem with the original @shadow idea. I don't
know of a real solution to this problem.
Imo, putting shadow file in a centralized location (the exact location
is irrelevant) is a wretched idea: it will add complexity, obscurity
and bugs not only to the code, but for users. I will never agree to
such a scheme. So I think the only thing for people to do is to
put .leo files that use @shadow in a writable directory :-) This is
the down side of Linux's security scheme.
Please comment now. I'll probably push revisions based on these
remarks tomorrow.
Edward
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
