Re: LyX 2.0.1 (OS X): file with relative path name not found
Patrick De Visschere writes: I normally use pathnames relative to the current directory and since . is automatically included in the TEXINPUTS prefix, this should still work I guess without making any modifications. But it doesn't. The problematic paths start with ../ and it looks there is still a problem with that. Yes, it seems that this a (wanted) Kpathsea feature(?): http://www.chemie.fu-berlin.de/chemnet/use/info/kpathsea/kpathsea_4.html#IDX118 If the filename being searched for is absolute or explicitly relative, i.e., starts with `/' or `./' or `../', Kpathsea simply checks if that file exists; it is not looked for along any paths. :( -- Enrico
Re: LyX 2.0.1 (OS X): file with relative path name not found
Patrick De Visschere writes: I normally use pathnames relative to the current directory and since . is automatically included in the TEXINPUTS prefix, this should still work I guess without making any modifications. But it doesn't. The problematic paths start with ../ and it looks there is still a problem with that. Yes, it seems that this a (wanted) Kpathsea feature(?): http://www.chemie.fu-berlin.de/chemnet/use/info/kpathsea/kpathsea_4.html#IDX118 If the filename being searched for is absolute or explicitly relative, i.e., starts with `/' or `./' or `../', Kpathsea simply checks if that file exists; it is not looked for along any paths. :( -- Enrico
Re: LyX 2.0.1 (OS X): file with relative path name not found
Patrick De Visschere writes: > > I normally use pathnames relative to the current directory and since . is > automatically included in the TEXINPUTS prefix, this should still work I > guess without making any modifications. But it doesn't. > The problematic paths start with ../ and it looks there is still a problem > with that. Yes, it seems that this a (wanted) Kpathsea feature(?): http://www.chemie.fu-berlin.de/chemnet/use/info/kpathsea/kpathsea_4.html#IDX118 If the filename being searched for is absolute or explicitly relative, i.e., starts with `/' or `./' or `../', Kpathsea simply checks if that file exists; it is not looked for along any paths. :( -- Enrico
Re: LyX 2.0.1 (OS X): file with relative path name not found
On 27 Sep, 2011, at 11:11 PM, Richard Heck wrote:
On 09/27/2011 04:47 PM, Patrick De Visschere wrote:
Hello,
Including a .pdf file with \includegraphics and with a relative pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/some_file.pdf}
results in a file not found error from the pdftex.def package.
When exporting as .tex and processing with e.g. TeXShop there is no problem.
This problem occurs with LyX 2.0.1 under OS X; (not with LyX 2.0.0)
There have been some changes to how LyX handles external paths. These
are noted in the RELEASE NOTES file. I would guess that is the source of
the problem. If you can't resolve it, post a note to the devel list.
Richard
Thanks.
It looks like I should have read the release notes, sorry.
I was indeed referring to files in ERT.
I normally use pathnames relative to the current directory and since . is
automatically included in the TEXINPUTS prefix, this should still work I guess
without making any modifications. But it doesn't.
The problematic paths start with ../ and it looks there is still a problem with
that. I can of course drop the starting ../ and add .. to the prefix list but
I'm reluctant to changing those paths since they will then not run anymore in
the previous versions.
Also, when exporting as latex the prefix is not included, as far as I can see
and when fixed for LyX2.0.1 the latex-file will now not run with TeXShop,
unless one can instruct TeXShop to use the same prefix list.
Regards,
P. De Visschere
Re: LyX 2.0.1 (OS X): file with relative path name not found
On 27 Sep, 2011, at 11:11 PM, Richard Heck wrote:
On 09/27/2011 04:47 PM, Patrick De Visschere wrote:
Hello,
Including a .pdf file with \includegraphics and with a relative pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/some_file.pdf}
results in a file not found error from the pdftex.def package.
When exporting as .tex and processing with e.g. TeXShop there is no problem.
This problem occurs with LyX 2.0.1 under OS X; (not with LyX 2.0.0)
There have been some changes to how LyX handles external paths. These
are noted in the RELEASE NOTES file. I would guess that is the source of
the problem. If you can't resolve it, post a note to the devel list.
Richard
Thanks.
It looks like I should have read the release notes, sorry.
I was indeed referring to files in ERT.
I normally use pathnames relative to the current directory and since . is
automatically included in the TEXINPUTS prefix, this should still work I guess
without making any modifications. But it doesn't.
The problematic paths start with ../ and it looks there is still a problem with
that. I can of course drop the starting ../ and add .. to the prefix list but
I'm reluctant to changing those paths since they will then not run anymore in
the previous versions.
Also, when exporting as latex the prefix is not included, as far as I can see
and when fixed for LyX2.0.1 the latex-file will now not run with TeXShop,
unless one can instruct TeXShop to use the same prefix list.
Regards,
P. De Visschere
Re: LyX 2.0.1 (OS X): file with relative path name not found
On 27 Sep, 2011, at 11:11 PM, Richard Heck wrote:
> On 09/27/2011 04:47 PM, Patrick De Visschere wrote:
>> Hello,
>>
>> Including a .pdf file with \includegraphics and with a relative pathname like
>>
>> \includegraphics{../path/to/file/starting/from/parent/directory/some_file.pdf}
>>
>> results in a "file not found" error from the pdftex.def package.
>>
>> When exporting as .tex and processing with e.g. TeXShop there is no problem.
>>
>> This problem occurs with LyX 2.0.1 under OS X; (not with LyX 2.0.0)
>>
> There have been some changes to how LyX handles external paths. These
> are noted in the RELEASE NOTES file. I would guess that is the source of
> the problem. If you can't resolve it, post a note to the devel list.
>
> Richard
>
Thanks.
It looks like I should have read the release notes, sorry.
I was indeed referring to files in ERT.
I normally use pathnames relative to the current directory and since . is
automatically included in the TEXINPUTS prefix, this should still work I guess
without making any modifications. But it doesn't.
The problematic paths start with ../ and it looks there is still a problem with
that. I can of course drop the starting ../ and add .. to the prefix list but
I'm reluctant to changing those paths since they will then not run anymore in
the previous versions.
Also, when exporting as latex the prefix is not included, as far as I can see
and when fixed for LyX2.0.1 the latex-file will now not run with TeXShop,
unless one can instruct TeXShop to use the same prefix list.
Regards,
P. De Visschere
Re: LyX 2.0.1 (OS X): file with relative path name not found
On 09/27/2011 04:47 PM, Patrick De Visschere wrote:
Hello,
Including a .pdf file with \includegraphics and with a relative pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/some_file.pdf}
results in a file not found error from the pdftex.def package.
When exporting as .tex and processing with e.g. TeXShop there is no problem.
This problem occurs with LyX 2.0.1 under OS X; (not with LyX 2.0.0)
There have been some changes to how LyX handles external paths. These
are noted in the RELEASE NOTES file. I would guess that is the source of
the problem. If you can't resolve it, post a note to the devel list.
Richard
Re: LyX 2.0.1 (OS X): file with relative path name not found
On Sep 27, 2011, at 4:47 PM, Patrick De Visschere wrote:
Hello,
Including a .pdf file with \includegraphics and with a relative
pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/
some_file.pdf}
results in a file not found error from the pdftex.def package.
When exporting as .tex and processing with e.g. TeXShop there is no
problem.
This problem occurs with LyX 2.0.1 under OS X; (not with LyX 2.0.0)
Regards,
P. De Visschere
Are you using \includegraphics in a TeX Code box?
Or through the insert graphics LyX interface?
The former will cause problems because of the way LyX does the Tex
compile in a temporary directory, which is not where your relative
path is pointing.
If you use the LyX interface, it resolves all of the paths before
passing it off to the latex command.
I have the same issue with the \includepdf command and have just
learned to use full path strings.
(Yes I know there is now a LyX dialog for this command)
Or I think you can define a default pathname in the preamble, but it
is kind of messy.
I am a bit puzzled why the behavior switched between 2.0.0 and 2.0.1?
But maybe someone on the dev team can help.
HTH
Steve
Re: LyX 2.0.1 (OS X): file with relative path name not found
On Sep 27, 2011, at 5:11 PM, Richard Heck wrote:
On 09/27/2011 04:47 PM, Patrick De Visschere wrote:
Hello,
Including a .pdf file with \includegraphics and with a relative
pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/
some_file.pdf}
results in a file not found error from the pdftex.def package.
When exporting as .tex and processing with e.g. TeXShop there is no
problem.
This problem occurs with LyX 2.0.1 under OS X; (not with LyX 2.0.0)
There have been some changes to how LyX handles external paths. These
are noted in the RELEASE NOTES file. I would guess that is the
source of
the problem. If you can't resolve it, post a note to the devel list.
Yes indeed, a welcome improvement!
See info here
http://www.lyx.org/announce/2_0_1.txt
I guess it is time for me to upgrade to 2.0.1
(and ignore my previous reply to this thread!)
Re: LyX 2.0.1 (OS X): file with relative path name not found
On 09/27/2011 04:47 PM, Patrick De Visschere wrote:
Hello,
Including a .pdf file with \includegraphics and with a relative pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/some_file.pdf}
results in a file not found error from the pdftex.def package.
When exporting as .tex and processing with e.g. TeXShop there is no problem.
This problem occurs with LyX 2.0.1 under OS X; (not with LyX 2.0.0)
There have been some changes to how LyX handles external paths. These
are noted in the RELEASE NOTES file. I would guess that is the source of
the problem. If you can't resolve it, post a note to the devel list.
Richard
Re: LyX 2.0.1 (OS X): file with relative path name not found
On Sep 27, 2011, at 4:47 PM, Patrick De Visschere wrote:
Hello,
Including a .pdf file with \includegraphics and with a relative
pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/
some_file.pdf}
results in a file not found error from the pdftex.def package.
When exporting as .tex and processing with e.g. TeXShop there is no
problem.
This problem occurs with LyX 2.0.1 under OS X; (not with LyX 2.0.0)
Regards,
P. De Visschere
Are you using \includegraphics in a TeX Code box?
Or through the insert graphics LyX interface?
The former will cause problems because of the way LyX does the Tex
compile in a temporary directory, which is not where your relative
path is pointing.
If you use the LyX interface, it resolves all of the paths before
passing it off to the latex command.
I have the same issue with the \includepdf command and have just
learned to use full path strings.
(Yes I know there is now a LyX dialog for this command)
Or I think you can define a default pathname in the preamble, but it
is kind of messy.
I am a bit puzzled why the behavior switched between 2.0.0 and 2.0.1?
But maybe someone on the dev team can help.
HTH
Steve
Re: LyX 2.0.1 (OS X): file with relative path name not found
On Sep 27, 2011, at 5:11 PM, Richard Heck wrote:
On 09/27/2011 04:47 PM, Patrick De Visschere wrote:
Hello,
Including a .pdf file with \includegraphics and with a relative
pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/
some_file.pdf}
results in a file not found error from the pdftex.def package.
When exporting as .tex and processing with e.g. TeXShop there is no
problem.
This problem occurs with LyX 2.0.1 under OS X; (not with LyX 2.0.0)
There have been some changes to how LyX handles external paths. These
are noted in the RELEASE NOTES file. I would guess that is the
source of
the problem. If you can't resolve it, post a note to the devel list.
Yes indeed, a welcome improvement!
See info here
http://www.lyx.org/announce/2_0_1.txt
I guess it is time for me to upgrade to 2.0.1
(and ignore my previous reply to this thread!)
Re: LyX 2.0.1 (OS X): file with relative path name not found
On 09/27/2011 04:47 PM, Patrick De Visschere wrote:
> Hello,
>
> Including a .pdf file with \includegraphics and with a relative pathname like
>
> \includegraphics{../path/to/file/starting/from/parent/directory/some_file.pdf}
>
> results in a "file not found" error from the pdftex.def package.
>
> When exporting as .tex and processing with e.g. TeXShop there is no problem.
>
> This problem occurs with LyX 2.0.1 under OS X; (not with LyX 2.0.0)
>
There have been some changes to how LyX handles external paths. These
are noted in the RELEASE NOTES file. I would guess that is the source of
the problem. If you can't resolve it, post a note to the devel list.
Richard
Re: LyX 2.0.1 (OS X): file with relative path name not found
On Sep 27, 2011, at 4:47 PM, Patrick De Visschere wrote:
Hello,
Including a .pdf file with \includegraphics and with a relative
pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/
some_file.pdf}
results in a "file not found" error from the pdftex.def package.
When exporting as .tex and processing with e.g. TeXShop there is no
problem.
This problem occurs with LyX 2.0.1 under OS X; (not with LyX 2.0.0)
Regards,
P. De Visschere
Are you using \includegraphics in a TeX Code box?
Or through the insert graphics LyX interface?
The former will cause problems because of the way LyX does the Tex
compile in a temporary directory, which is not where your relative
path is pointing.
If you use the LyX interface, it resolves all of the paths before
passing it off to the latex command.
I have the same issue with the \includepdf command and have just
learned to use full path strings.
(Yes I know there is now a LyX dialog for this command)
Or I think you can define a default pathname in the preamble, but it
is kind of messy.
I am a bit puzzled why the behavior switched between 2.0.0 and 2.0.1?
But maybe someone on the dev team can help.
HTH
Steve
Re: LyX 2.0.1 (OS X): file with relative path name not found
On Sep 27, 2011, at 5:11 PM, Richard Heck wrote:
On 09/27/2011 04:47 PM, Patrick De Visschere wrote:
Hello,
Including a .pdf file with \includegraphics and with a relative
pathname like
\includegraphics{../path/to/file/starting/from/parent/directory/
some_file.pdf}
results in a "file not found" error from the pdftex.def package.
When exporting as .tex and processing with e.g. TeXShop there is no
problem.
This problem occurs with LyX 2.0.1 under OS X; (not with LyX 2.0.0)
There have been some changes to how LyX handles external paths. These
are noted in the RELEASE NOTES file. I would guess that is the
source of
the problem. If you can't resolve it, post a note to the devel list.
Yes indeed, a welcome improvement!
See info here
http://www.lyx.org/announce/2_0_1.txt
I guess it is time for me to upgrade to 2.0.1
(and ignore my previous reply to this thread!)
