On 03/22/2014 09:28 PM, Uwe Stöhr wrote:
Am 22.03.2014 15:19, schrieb Stephan Witt:
This must be some misunderstanding. We are talking about user
preferences.
The preferences of your colleague are living in a complete "parallel
universe".
You shouldn't have any access to them. Nobody said the administrator
should
copy any user preferences for any user.
What happens if the admin account starts LyX and LyX fnd the
preferences of user A and user B?
LyX looks only for preferences associated with currently running account.
Assuring this is impossible at installation time and during the
first start of LyX too. How should LyX know if an existing
preference is a working one and the one used by the current user for
LyX 2.0.x?
For example at work I use a network drive that is mapped so that I
can grab the LyX settings I need at any time from there.
What is with the cases that LyX 2.0.x was once installed and later
on removed but the preferences were not deleted?
Then the preferences will be copied. Why not?
I already explained that this can lead to a LyX that is not working.
You assume a certain usage of LyX that is not always the case. What is
the number one text engine? - MS Windows. So people are using LyX only
for certain documents like a thesis, a scientific paper, a scientific
report etc. So even at the university I often had the case that users
don't use LyX for months. However the only important thing is that LyX
is uninstalled meanwhile by some users (unimportant why). By default
LyX is then removed but the preferences are left on the PC. (This is
the default uninstaller setting which was the result of a discussion
long time ago on the lyx-users list.) OK, now the user wants to use
LyX again because he remembered it or because he heard that there is a
new version with new features hew might like t try out. If you then
use the old preferences file you will destroy the new one built by the
installer. So e.g. you will replace LyX's PATH_prefix with some
outdated/no longer existing paths stored in the old preferences file.
It seems to me wrong to design our installer for this kind of case, and
to make things complicated for frequent users who are upgrading.
Richard