> As I said, I just don't care for this attitude. These are our problems,
> not the users'. and simply declaring that there's no other way is just,
> well, not productive.
This is *not* our problem. Users want to use the *same* file on
different systems, but this file can not be presented as th
Bo Peng wrote:
> You are talking about the worst scenario
>
No, this is the normal scenario, at least on any system other than
Windows: Absolute paths to files in my user tree will not be writable on
(almost) any other system. And writing the file somewhere else breaks
the LyX file.
On Mon, Mar 31, 2008 at 3:54 PM, Richard Heck <[EMAIL PROTECTED]> wrote:
> Bo Peng wrote:
You skipped that read-only problem your approach has. :-)
> This is not how it is in my work. ... Actually, that's
> not quite true. *I* could use it, because *I* know to make sure all our
> shared files
Bo Peng wrote:
And let's remember that extraction is likely to happen a lot. As Bo said
before, the normal way of working will be to receive a file, extract it,
and then work unbundled, so that e.g. you can edit biblio.bib without
having to hunt down
/tmp/lyx_tmpdir81735JCJRk/lyx_tmpbuf2/Ly
> 1. If /usr/share/lyx/doc/UserGuide.lyx were bundled and you wanted to
> extract it, you would be stuck, because you can't write to
> /usr/share/lyx/doc/.
We always extract to the writable temp directory. Unbundle a readonly
file is disabled, because unbundling will change the file status.
Usi
Bo Peng wrote:
On Sun, Mar 30, 2008 at 5:57 AM, Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
rgheck wrote:
> So I keep thinking that the solution to this is that whenever you open a
> bundled file, it immediately unbundles itself and uses the unbundled
> files, just like a normal LyX file
On Sun, Mar 30, 2008 at 5:57 AM, Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
> rgheck wrote:
>
> > So I keep thinking that the solution to this is that whenever you open a
> > bundled file, it immediately unbundles itself and uses the unbundled
> > files, just like a normal LyX file would. In t
rgheck wrote:
So I keep thinking that the solution to this is that whenever you open a
bundled file, it immediately unbundles itself and uses the unbundled
files, just like a normal LyX file would. In that case, bundling has
only to do with how the file is opened and saved and nothing to do wi
Bo Peng wrote:
> In the very first version of my embedding design, I have something
> called AUTO embedding mode. That is to say, an embedded file in this
> mode will automatically use an external version when it exists. That
> proposal was disliked by all other developers.
>
>
Because it
> > In the very first version of my embedding design, I have something
> > called AUTO embedding mode. That is to say, an embedded file in this
> > mode will automatically use an external version when it exists. That
> > proposal was disliked by all other developers.
> >
> >
> Because it los
10 matches
Mail list logo
