Pavel Sanda wrote:
Steve Litt wrote:
On Wednesday 08 July 2009 12:25:32 pm Pavel Sanda wrote:
hi,
is there some reason we treat softlinks to files as the same files?
i have this setup:
0) master including 1,2,3
1) a/1.lyx
2) b/1.lyx
3) c/1.lyx
where 2 and 3 is symlinked to 1.
i want that 2 and 3 both have different local pictures and different
insetinfo buffer-path, however lyx treat 2 and 3 as identical to 1 either
when trying to edit them separately from master include contex menu or
when typeseting via latex - i get three times a/1.lyx .
would it cause some problems to distinguish between symlinks?
pavel
The whole purpose of symlinks (and hard links for that matter) is to link
multiple names to the same file.
of course, but from that doesn't follow that inset info show path of another
file.
also we should use the images b/image.eps for file b/1.lyx. and we do it --
the problem appears once master/child bussiness comes into play.
Your complaint is the intended behavior.
it is not intended since such kind of scenario won't come to your mind until
you get this clash ;) the fact the we care those files in a different fashion
when you open directly b/1.lyx and when you open it through master document
just prove it.
Don't symlink them, and you'll get what you want.
no, i dont want to care about the same text 3-times.
pavel
Use hard links instead then.
(ln a/1.lyx b/1.lyx instead of ln -s a/1.lyx b/1.lyx)
I just tested it, and hard links do what you want. The two
hardlinked documents includes different files.
Of course, saving changes to both files could be messy, but I see no
problem. When the user uses links to save work like this, then surely
the user knows what is happening and won't stupidly edit both files.
The beginner who don't know about links, will probably not use them like
this.
Helge Hafting
