On 31/03/2011 21:09, Hans-Peter Diettrich wrote:
Martin schrieb:
This whole discussion seems to mix 2 issues into one:
- problems caused by using the wrong config due to none awareness
(imho the main issue)
- convenience of using multiply configs.
The first problem disappears as soon as a config resides in the
Lazarus directory, next the EXE file. Then Lazarus will definitiely
use that config, and nothing can be screwed up by omission of a pcp.
No, well only if....
...let me explain a bit more what I tried to explain before (and had in
my last mail too)
It would only help, if you totally abandon all global config. don't even
look for a global anymore, only check the exe folder, nowhere else.
But if the search order for config would be:
- exe-dir
- global as current
Then as soon as a global config exist you are back to were you are now.
- download a new lazarus, into some folder "lazfoo"
- now lazfoo does not yet contain config, but the global folder does.
so in your way, one has to first create a config in lazfoo.
This is an explicit action the user must undertake, same as adding the
-pcp.
=> But if the user is unaware of the issue, he will not ad that config
to lazfoo, and run with the global config => same as now
Let me guess, now you say, then every lazarus should come with a local
config?
That is the same as abandoning the global config completely (because if
always a local conf exists, it will always use the local, never the
global) => but the proposal was an optional local, that would be found
first, if and only if present.
So were (or how) exactly, in which scenario, does an additional search
for a local config actual help the unaware user?
Sure, once you know,it may be more convenient to some, but a startup
script is no less convenient to most.
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
