> The only real question is I am happy to hear this.
> where to store the > information about the original location of the file, so you can do the > "update from external file" thing. Whether there is just a copy in the > bundle isn't the issue. Your version has a copy in the bundle, too. But you > keep a kind of link to the original file by storing the original pathname in > the LyX file. Jose's idea was that this isn't cross-platform, so we should > store it somewhere else. But you keep the connection---on the only machine > where it works---either way. Basically, we disagree on the 'only machine' part. As I have said, I have multiple trees on different machines, and I guess this is not unusual for anyone using a repository to save his files. You also have my "this is used now" argument. You do not have a convincing argument if you do not want to do what you are proposing to *all* insets, because of the problems it causes. Lastly, if we extract to a special folder $DOC_PATH/Lyx.Embed.Abs/abs/path, we do not really need to change the inset. Of course the EmbeddedFile code would be more complicated because there can be /abs/path and $DOC_PATH/LyX.Embed.Abs/abs/path depending on the existence of /abs/path, but this would solve the last piece of non-reversibility of my approach. You are right that a document may not be unbundled *completely* on all OS if different full path names are used, but I would consider this as an advantage. The lyx file would unbundle and compile successfully on all OS. Cheers, Bo
