Re: Relative paths

Le 04/05/2015 00:44, Enrico Forestieri a écrit : Unless someone can give an example showing that a relative path of one of the above forms produces problems, I am going to unify the two methods in a single one simply returning a relative path. Using relative paths is a superior alternative

Re: Relative paths

returning a relative path. Using relative paths is a superior alternative to absolute ones, but currently LyX can return an absolute path when a relative one is actually possible. A relative path is always possible, at least in linux: think ../../home/foo/myfiles/foo.lyx which is actually

Re: Relative paths

below). Except that my homedir is /home/lasgoutt/ :) Another example: if I have some image files in ~/lib/images/ and they are referred to as relative paths, then I cannot move freely my lyx file in another directory, only save-as will do. This is not intuitive either. Nothing wrong if you

Re: Relative paths

to as relative paths, then I cannot move freely my lyx file in another directory, only save-as will do. This is not intuitive either. This is also true if you have your images in a doc subdir. You have to move the whole subtree. Then, it is not uncommon having a figs directory alongside a docs directory

Re: Relative paths

Le 04/05/2015 00:44, Enrico Forestieri a écrit : Unless someone can give an example showing that a relative path of one of the above forms produces problems, I am going to unify the two methods in a single one simply returning a relative path. Using relative paths is a superior alternative

Re: Relative paths

n a single one simply returning a relative path. > > > >Using relative paths is a superior alternative to absolute ones, but > >currently LyX can return an absolute path when a relative one is > >actually possible. > > A relative path is always possible, at least

Re: Relative paths

below). Except that my homedir is /home/lasgoutt/ :) Another example: if I have some image files in ~/lib/images/ and they are referred to as relative paths, then I cannot move freely my lyx file in another directory, only save-as will do. This is not intuitive either. Nothing wrong if you

Re: Relative paths

other example: if I have some image files in ~/lib/images/ and they are > referred to as relative paths, then I cannot move freely my lyx file in > another directory, only save-as will do. This is not intuitive either. This is also true if you have your images in a doc subdir. You have to move the

Re: Relative paths

On Sun, May 3, 2015 at 6:44 PM, Enrico Forestieri for...@lyx.org wrote: The two methods browseRelToParent() and browseRelToSub() in GuiView.cpp both return a relative path. The only difference is that the first one returns an absolute path if it would start with ../, and the second one if it

Re: Relative paths

On Sun, May 03, 2015 at 07:00:06PM -0400, Scott Kostyshak wrote: On Sun, May 3, 2015 at 6:44 PM, Enrico Forestieri for...@lyx.org wrote: The two methods browseRelToParent() and browseRelToSub() in GuiView.cpp both return a relative path. The only difference is that the first one returns an

Relative paths

. Using relative paths is a superior alternative to absolute ones, but currently LyX can return an absolute path when a relative one is actually possible. -- Enrico

Re: Relative paths

On 05/03/2015 08:13 PM, Enrico Forestieri wrote: On Sun, May 03, 2015 at 07:00:06PM -0400, Scott Kostyshak wrote: On Sun, May 3, 2015 at 6:44 PM, Enrico Forestieri for...@lyx.org wrote: The two methods browseRelToParent() and browseRelToSub() in GuiView.cpp both return a relative path. The

Relative paths

ne simply returning a relative path. Using relative paths is a superior alternative to absolute ones, but currently LyX can return an absolute path when a relative one is actually possible. -- Enrico

Re: Relative paths

On Sun, May 3, 2015 at 6:44 PM, Enrico Forestieri wrote: > The two methods browseRelToParent() and browseRelToSub() in GuiView.cpp > both return a relative path. The only difference is that the first one > returns an absolute path if it would start with "../", and the second one >

Re: Relative paths

On Sun, May 03, 2015 at 07:00:06PM -0400, Scott Kostyshak wrote: > On Sun, May 3, 2015 at 6:44 PM, Enrico Forestieri wrote: > > The two methods browseRelToParent() and browseRelToSub() in GuiView.cpp > > both return a relative path. The only difference is that the first one > >

Re: Relative paths

On 05/03/2015 08:13 PM, Enrico Forestieri wrote: On Sun, May 03, 2015 at 07:00:06PM -0400, Scott Kostyshak wrote: On Sun, May 3, 2015 at 6:44 PM, Enrico Forestieri wrote: The two methods browseRelToParent() and browseRelToSub() in GuiView.cpp both return a relative path. The

new [regression]: relative paths are no longer handled by LyX

Whenever you open a document, for example the UserGuide and save it, all relative paths are changed to absolute ones. This prevents any work on the documentation as it makes the documents uncompilable. This could be a side effect of the Embedded files removal. Richard? thanks and regards Uwe

Re: new [regression]: relative paths are no longer handled by LyX

Uwe Stöhr wrote: Whenever you open a document, for example the UserGuide and save it, all relative paths are changed to absolute ones. This prevents any work on the documentation as it makes the documents uncompilable. This could be a side effect of the Embedded files removal. Richard

new [regression]: relative paths are no longer handled by LyX

Whenever you open a document, for example the UserGuide and save it, all relative paths are changed to absolute ones. This prevents any work on the documentation as it makes the documents uncompilable. This could be a side effect of the Embedded files removal. Richard? thanks and regards Uwe

Re: new [regression]: relative paths are no longer handled by LyX

Uwe Stöhr wrote: Whenever you open a document, for example the UserGuide and save it, all relative paths are changed to absolute ones. This prevents any work on the documentation as it makes the documents uncompilable. This could be a side effect of the Embedded files removal. Richard

Re: Request - relative paths for BibTeX references (maybe only relevant for Windows port)

Both file dialogs should work alike in theory: Return a relative filename if the file is in the document directory or a subdirectory thereof, and return an absolute filename if not. Do you get different behaviour? Yes, with LyX 1.3.5 qt (Windows port). Ekkehart

Re: Request - relative paths for BibTeX references (maybe only relevant for Windows port)

Both file dialogs should work alike in theory: Return a relative filename if the file is in the document directory or a subdirectory thereof, and return an absolute filename if not. Do you get different behaviour? Yes, with LyX 1.3.5 qt (Windows port). Ekkehart

Request - relative paths for BibTeX references (maybe only relevant for Windows port)

Just a small suggestion: If BibTeX reference is inserted and the bibliography file is searched for and selected, its reference is given as the absolute path, rather than the relative path. To enhance portability, it would be good to take the relative path, as done with the graphics entries.

Re: Request - relative paths for BibTeX references (maybe only relevant for Windows port)

Am Mittwoch, 13. April 2005 10:16 schrieb Ekkehart Schlicht: Just a small suggestion: If BibTeX reference is inserted and the bibliography file is searched for and selected, its reference is given as the absolute path, rather than the relative path. To enhance portability, it would be good

Request - relative paths for BibTeX references (maybe only relevant for Windows port)

Just a small suggestion: If BibTeX reference is inserted and the bibliography file is searched for and selected, its reference is given as the absolute path, rather than the relative path. To enhance portability, it would be good to take the relative path, as done with the graphics entries.

Re: Request - relative paths for BibTeX references (maybe only relevant for Windows port)

Am Mittwoch, 13. April 2005 10:16 schrieb Ekkehart Schlicht: > Just a small suggestion: > > If BibTeX reference is inserted and the bibliography file is searched for > and selected, its reference is given as the absolute path, rather than > the relative path. To enhance portability, it would be

Re: [PATCH 13x, 14x] package and relative paths from PATH

Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus The attached patches enable the lyx executable to be found from Angus the PATH environment variable if it expands to elements with Angus relative paths. Angus Confirmed as working and fixes a clear bug so I'm committing to Angus both trees

Re: [PATCH 13x, 14x] package and relative paths from PATH

>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> The attached patches enable the lyx executable to be found from Angus> the PATH environment variable if it expands to elements with Angus> relative paths. Angus> Confirmed as work

[PATCH 13x, 14x] package and relative paths from PATH

The attached patches enable the lyx executable to be found from the PATH environment variable if it expands to elements with relative paths. Confirmed as working and fixes a clear bug so I'm committing to both trees now. -- AngusIndex: src/support/ChangeLog

[PATCH 13x, 14x] package and relative paths from PATH

The attached patches enable the lyx executable to be found from the PATH environment variable if it expands to elements with relative paths. Confirmed as working and fixes a clear bug so I'm committing to both trees now. -- AngusIndex: src/support/ChangeLog

Suggestion: Relative paths for figures

Hi developers I have been using LyX for some time now, but working with figures is rather new to me. I am starting to understand it, but there is still a way to go with all those graphics formats, compilers and ImageMagic. Geee. ;-) I have noticed that LyX by default works with absolute

Re: Suggestion: Relative paths for figures

On Wednesday 24 March 2004 09:38, Janus Sandsgaard wrote: Hi developers [...] I have noticed that LyX by default works with absolute paths if you use the browse-feature to point out your figures. I find this to be a little annoying and and can't see the pratical reason why it works this way.

Re: Suggestion: Relative paths for figures

On Wednesday 24 March 2004 10:56, Jose' Matos wrote: What is the lyx version you are using? LyX 1.3.2. I stick to the packages privided by SuSE and they are not up2date. I think that this bug was fixed for the qt version in 1.3.3 (+/-). That explain things. I am happy to hear. You LyX

Re: Suggestion: Relative paths for figures

Jose' Matos wrote: On Wednesday 24 March 2004 09:38, Janus Sandsgaard wrote: Hi developers [...] I have noticed that LyX by default works with absolute paths if you use the browse-feature to point out your figures. I find this to be a little annoying and and can't see the pratical reason

Re: Suggestion: Relative paths for figures

Georg == Georg Baum [EMAIL PROTECTED] writes: Georg It inserts the relative name if the file is in the same Georg directory (1.3.5cvs, qt, I have no older version anymore). Georg It does not if the file is above, e. g. ../../other/dir/a.eps Georg gets converted to the absolute path, but I

Suggestion: Relative paths for figures

Hi developers I have been using LyX for some time now, but working with figures is rather new to me. I am starting to understand it, but there is still a way to go with all those graphics formats, compilers and ImageMagic. Geee. ;-) I have noticed that LyX by default works with absolute

Re: Suggestion: Relative paths for figures

On Wednesday 24 March 2004 09:38, Janus Sandsgaard wrote: > Hi developers [...] > I have noticed that LyX by default works with absolute paths if you use > the browse-feature to point out your figures. I find this to be a little > annoying and and can't see the pratical reason why it works this

Re: Suggestion: Relative paths for figures

On Wednesday 24 March 2004 10:56, Jose' Matos wrote: > What is the lyx version you are using? LyX 1.3.2. I stick to the packages privided by SuSE and they are not up2date. > I think that this bug was fixed for the qt version in 1.3.3 (+/-). That explain things. I am happy to hear. You LyX

Re: Suggestion: Relative paths for figures

Jose' Matos wrote: > On Wednesday 24 March 2004 09:38, Janus Sandsgaard wrote: >> Hi developers > [...] >> I have noticed that LyX by default works with absolute paths if you use >> the browse-feature to point out your figures. I find this to be a little >> annoying and and can't see the pratical

Re: Suggestion: Relative paths for figures

> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes: Georg> It inserts the relative name if the file is in the same Georg> directory (1.3.5cvs, qt, I have no older version anymore). Georg> It does not if the file is above, e. g. ../../other/dir/a.eps Georg> gets converted to the absolute

Re: InsetGraphics and relative paths don't mix well

Angus == Angus Leeming [EMAIL PROTECTED] writes: Angus On Thursday 14 February 2002 4:23 pm, John Levon wrote: perhaps even better would be to secretly store both the relative and Angus absoluate paths. That way the document then also has a chance of surviving a mv, Angus because we look

Re: InsetGraphics and relative paths don't mix well

> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: Angus> On Thursday 14 February 2002 4:23 pm, John Levon wrote: >> perhaps even better would be to secretly store both the relative >> and Angus> absoluate >> paths. That way the document then also has a chance of surviving a >> "mv",

Re: InsetGraphics and relative paths don't mix well

Allan == Allan Rae [EMAIL PROTECTED] writes: Allan I have a figure at: Allan ../common/new-banner.png Allan that I'm using in a document. PDFLaTeX is able to find and Allan render it but InsetGraphics complains with an error message Allan (Alert dialog) that the file either doesn't exist or

Re: InsetGraphics and relative paths don't mix well

On Thu, Feb 14, 2002 at 12:05:33PM +0100, Jean-Marc Lasgouttes wrote: I think insetgraphics should treat all file names as relative to buffer directory. definitely because then it also allows : /home/moz/mypictures/picture.png so both cases would be covered fine perhaps even better would

Re: InsetGraphics and relative paths don't mix well

> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes: Allan> I have a figure at: Allan> ../common/new-banner.png Allan> that I'm using in a document. PDFLaTeX is able to find and Allan> render it but InsetGraphics complains with an error message Allan> (Alert dialog) that the file either

Re: InsetGraphics and relative paths don't mix well

On Thu, Feb 14, 2002 at 12:05:33PM +0100, Jean-Marc Lasgouttes wrote: > I think insetgraphics should treat all file names as relative to buffer > directory. definitely because then it also allows : /home/moz/mypictures/picture.png so both cases would be covered fine perhaps even better

InsetGraphics and relative paths don't mix well

I have a figure at: ../common/new-banner.png that I'm using in a document. PDFLaTeX is able to find and render it but InsetGraphics complains with an error message (Alert dialog) that the file either doesn't exist or is unreadable. When I have the location above entered in the

InsetGraphics and relative paths don't mix well

I have a figure at: ../common/new-banner.png that I'm using in a document. PDFLaTeX is able to find and render it but InsetGraphics complains with an error message (Alert dialog) that the file either doesn't exist or is unreadable. When I have the location above entered in the