Le 04/05/2015 17:37, Enrico Forestieri a écrit :
A relative path is always possible, at least in linux: think
../../home/foo/myfiles/foo.lyx
which is actually an absolute path to a file in another user's homedir.
Wrong example. The relative path would be ../foo/myfiles/foo.lyx (but
see below).
Except that my homedir is /home/lasgoutt/ :)
Another example: if I have some image files in ~/lib/images/ and they
are referred to as relative paths, then I cannot move freely my lyx file
in another directory, only save-as will do. This is not intuitive either.
Nothing wrong if you always work on the same computer and do not
collaborate with others. The way LyX deals with relative paths is
an arbitrary obstacle to collaborative work. If all paths were
relative, I could make an archive starting from root (/) like this:
usr/local/texfiles/.....
home/user/figs/....
home/user/docs/...
I would hate to receive from somebody a tar file that creates an
arbitrary complicated directory tree on my harddisk. And then I have to
remember that the .lyx file I want to edit is in
home/forenr/papers/work_with_jean_marc/new/updated/article.lyx ?
If I want to collaborate, I put all the relevant files in a directory in
a nicely organized manner. And then LyX will just do what is needed.
Collaborating has a price in terms of a little bit of organization.
There is nothing wrong with that.
But LyX, stubbornly insists in not using relative paths in certain
cases based on an arbitrary decision.
As far as I know, LyX proposes, it does not insist if you decide to
change the path returned by Browse...
JMarc
