On 09/19/2011 02:33 AM, Pavel Sanda wrote:
Liviu Andronic wrote:
On Mon, Sep 19, 2011 at 3:04 AM, Tommaso Cucinotta<tomm...@lyx.org> wrote:
AFAICS, it would not be bad to have an option with which LyX tries to ignore
what is not understood in future file-formats, and simply goes on trying to
execute anyway (e.g., --keep-going a'la make). For example, in the RC file
This allows for the possibility of LyX opening the file nonetheless
while corrupting/truncating some feature and without the user's
knowledge. Very dangerous.
i'm having similar thoughts.
In its present state, too, LyX is likely to do very weird things (e.g.,
interpret inset arguments as plain text), if not crash, since it will
get confused about where it is in the parsing. If we had a structured
(e.g., XML) format, then we could ignore everything within the tags we
don't recognize, but the format is not well enough defined to do this as
things now are.
development lyx2lyx routines are not widely
tested and go through changes as the time passes, remember pre 2.0.0
carneval of hundred commits when Richard got inspired by higher spirits ;)
Or lower ones.
As LIviu mentioned, the issues here have been discussed before. If
someone wants to try the auto-download lyx2lyx option, they can
certainly do that. Remember that you need to download the whole lyx2lyx/
directory, really, to be safe. We could also put something in the docs,
explaining what to do, and point users to it. (If there's a worry about
things being over-written, people can put what they download into
$USER_DIR/lyx2lyx/, and we can make that work if it doesn't.
But honestly, we go to great lengths to preserve compatibility already,
and if people are using versions older than 1.6.10, they should upgrade.
if there is a need to cooperate on 1.6 documents we may think of the feature
present in openoffice which asks you to stay on old format before saving...
Of course, the final release of each series has the lyx2lyx from the
next one.
All of that said, the issue that started this, as I recall, had to do
with a failure to parse the preferences file. In that case, surely, LyX
should just start, throwing a warning, and perhaps asking if the user
would like to erase the invalid file and start afresh. That ought to be
easy enough to do.
Richard
