> "Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
>
> | What's wrong with offering to rename the directory?
>
> That you suddenly might break all the other programs that used this
> dir without your knowledge?
As long as it is the choice of the user, I don't see the
problem.
To make the discussion more concrete, let me outline
exactly what I propose:
If the user has a document with a path with a space in it,
use-temp-dir is false, and LyX is about to invoke LaTeX on
the document, the following dialog appears:
Ha! You fool! You are trying to typeset a document with
a space in the path to the document. If you did your
homework, you'd know that LaTeX is completely flawed and
don't understand such paths.
Now, what are we gonna do?
1) Press Cancel to forget about typesetting this document for now,
and fix LaTeX to work with spaces in paths. Then come
back to the LyX team and say that this dialog is not
needed anyway.
2) Press Rename directory to rename the offending directory
to Foo_bar_cant_fool_me. Notice that this might affect
other open documents in other applications, but it would
if you tried to rename in the shell anyway.
3) Press Use temp-directory to typeset the document in a
temporary directory. If you are lucky and have a decent
file-system, we won't have to copy the document, but can
use a link instead, but if you are not, we have to make a
full temporary copy.
So, make up your mind, please.
What I understand from the different outbursts is that 2) is
considered too wild, because it can wreak havoc if you have
other files open in other applications. (Unless you use
Windows of course, since that will tell you exactly what
files are open and would be affected, but I suppose that
does not matter in this context.)
As I see it, option 2) is the most user friendly, because that
will solve the problem for the user in most cases where you, facing
the problem, would want to act to solve it.
Also, it could prevent problems with other implicitly referenced
documents, which is harder to do with 3) AFAICS.
But, personally, I think this problem is so rare in practice
that it would in fact be satisfactory if LyX just provided 1).
In fact, I would even be willing to just settle this by adding
a new FAQ and leaving the code alone.
Greets,
Asger
