"Bo Peng" <[EMAIL PROTECTED]> writes:

> I do not think you understand the problem well enough. Yes, I save the
> original path, I read, if possible, that external file, but I do not
> write to that external file. My proposal now only unbundle to document
> directory. There is no 'modify stuff that is outside its scope', so I
> do not think there is any security issue here. Jose's concern was that
> I should not save such a file *name* in .lyx file.

OK then. To be frank, I did not manage to read all the threads as
carefully as may be necessary.

So all you do is remember the source of a bundled file if is is
outside of document directory, right? In this case I agree with Jose
that remembering it in lyx session stuff makes more sense, since it
allows to have a different place for the external file in each user
setting, which is in the end much more configurable that what you
propose. And then there is no question about translating absolute
path names between different architectures.

JMarc

Reply via email to