Pavel Sanda wrote:
see why you might want to do what you describe. Perhaps in that case we
should only allow these buffers to be opened read-only?
very good idea. should i bugzilla it?
Sure.
rh
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 .
>>
>> wo
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 --
-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?
We used to do so, and it did cause bugs. (This is
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
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. Your complaint is the intended behavior.
Don't symlink them, and you'll get what you want.
SteveT
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
; Are there platforms on which we want LyX to run that don't handle
>>>> symlinks?
>>>>
>>> You mean Windows?
>>>
>> Except Vista, as I've learned. I had thought Windows did do symlinks but
>> not hard links, but apparently only by che
On Thu, 24 May 2007, Richard Heck wrote:
Andre Poenitz wrote:
On Wed, May 23, 2007 at 04:09:50PM -0400, Richard Heck wrote:
Is it safe to use the create_symlink function from boost::filesystems?
Are there platforms on which we want LyX to run that don't handle symlinks?
You mean Wi
Andre Poenitz wrote:
> On Wed, May 23, 2007 at 04:09:50PM -0400, Richard Heck wrote:
>
>> Is it safe to use the create_symlink function from boost::filesystems?
>> Are there platforms on which we want LyX to run that don't handle symlinks?
>>
> You mean Win
On Wed, May 23, 2007 at 04:09:50PM -0400, Richard Heck wrote:
> Is it safe to use the create_symlink function from boost::filesystems?
> Are there platforms on which we want LyX to run that don't handle symlinks?
You mean Windows?
Andre'
Jean-Marc Lasgouttes wrote:
> Richard> So does this seems sensible?
>
> Why do you want symlinks actually?
It's not a big deal, but the solution I've worked out to various
problems with the converter code (e.g., in the case of htlatex) involves
copying the file we're
>>>>> "Richard" == Richard Heck <[EMAIL PROTECTED]> writes:
Richard> So does this seems sensible?
Why do you want symlinks actually?
JMarc
Jean-Marc Lasgouttes wrote:
> Richard> Is it safe to use the create_symlink function from
> Richard> boost::filesystems? Are there platforms on which we want LyX
> Richard> to run that don't handle symlinks?
>
> Windows?
>
So does this seems sensible?
namesp
Jean-Marc Lasgouttes wrote:
> Richard> Is it safe to use the create_symlink function from
> Richard> boost::filesystems? Are there platforms on which we want LyX
> Richard> to run that don't handle symlinks?
>
> Windows?
>
I thought Windows did do symlinks but n
>>>>> "Richard" == Richard Heck <[EMAIL PROTECTED]> writes:
Richard> Is it safe to use the create_symlink function from
Richard> boost::filesystems? Are there platforms on which we want LyX
Richard> to run that don't handle symlinks?
Windows?
JMarc
Is it safe to use the create_symlink function from boost::filesystems?
Are there platforms on which we want LyX to run that don't handle symlinks?
--
==
Richard G Heck, Jr
Professor of Philosophy
Brown University
> "Peter" == Peter J Braam <[EMAIL PROTECTED]> writes:
Peter> Hi, Just another thought:
Peter> I have no idea if Windows shortcuts can be accomodated easily,
Peter> it would be great if at least the Qt file browser could handle
Peter> them. Any ideas?
Hello,
A somewhat late answer: if the
> "Kuba" == Kuba Ober <[EMAIL PROTECTED]> writes:
>> I have no idea if Windows shortcuts can be accomodated easily, it
>> would be great if at least the Qt file browser could handle them.
>> Any ideas?
Kuba> IIRC if you don't get too fancy the Qt file browser simply
Kuba> launches a standard
> I have no idea if Windows shortcuts can be accomodated easily, it would
> be great if at least the Qt file browser could handle them. Any ideas?
IIRC if you don't get too fancy the Qt file browser simply launches a standard
windows dialog box which IIRC handles shortcuts fine? As long as it re
Hi,
Just another thought:
I have no idea if Windows shortcuts can be accomodated easily, it would
be great if at least the Qt file browser could handle them. Any ideas?
- Peter -
> "Darren" == Darren Freeman <[EMAIL PROTECTED]> writes:
Darren> OK, so just add a cp -s to the makefile? It should for the
Darren> most part be safe to assume the docs are checked out next to
Darren> the sources, or if really adventurous add a check for the docs
Darren> in the configure scrip
On Tue, 2003-03-18 at 01:55, Jean-Marc Lasgouttes wrote:
> >>>>> "Darren" == Darren Freeman <[EMAIL PROTECTED]> writes:
> Darren> What I suggest is that the lyx-devel repository come with
> Darren> either a) an extension to the makefile which adds re
sitory come with
Darren> either a) an extension to the makefile which adds relative
Darren> symlinks as appropriate, or b) some symlinks to the current
Darren> lyxdoc contents.
What about something simpler: have a variable LYX_DOCDIR_14x that can
point to the documentation files.
However, do
Dear List,
The CVS versions of LyX obviously don't come with docs, they're in
another module checked out separately.
What I suggest is that the lyx-devel repository come with either a) an
extension to the makefile which adds relative symlinks as appropriate,
or b) some symlinks to t
25 matches
Mail list logo
