PhilipPirrip wrote:
> I suspect the other slash was added as a bug fix for those OS's that do
> not have it at the end of the path, can't see any other reason.
> So I suppose this should be tested on OSX and Windows as well.
It is not an OS issue. LyX has an OS abstraction layer for this kind of
Thanks Georg, I hope we'll eventually get somewhere.
On 08/26/2015 04:42 PM, Georg Baum wrote:
What do others think? Should we remove the second slash? I tend to say yes,
since I could not find any documentation about it.
I suspect the other slash was added as a bug fix for those OS's that
Thanks Georg, I hope we'll eventually get somewhere.
On 08/26/2015 04:42 PM, Georg Baum wrote:
What do others think? Should we remove the second slash? I tend to say yes,
since I could not find any documentation about it.
I suspect the other slash was added as a bug fix for those OS's that
PhilipPirrip wrote:
Why does \input@path end with two slashes, as in
/home/user/directory//
IIRC this means that also sub directories are searched, but this should
be documented in some TeX or LaTeX docs.
Not sure how it all works for (La)TeX, I'm assuming this is all handled
by the OS.
PhilipPirrip wrote:
> Why does \input@path end with two slashes, as in
> /home/user/directory//
IIRC this means that also sub directories are searched, but this should
be documented in some TeX or LaTeX docs.
>
> Not sure how it all works for (La)TeX, I'm assuming this is all
PhilipPirrip wrote:
On 08/19/2015 04:44 PM, Georg Baum wrote:
PhilipPirrip wrote:
Why does \input@path end with two slashes, as in
/home/user/directory//
IIRC this means that also sub directories are searched, but this should
be documented in some TeX or LaTeX docs.
I did some reserach,
Why does \input@path end with two slashes, as in
/home/user/directory//
IIRC this means that also sub directories are searched, but this should
be documented in some TeX or LaTeX docs.
Not sure how it all works for (La)TeX, I'm assuming this is all handled
by the OS. Unixoids (OSX, Linux)
PhilipPirrip wrote:
> On 08/19/2015 04:44 PM, Georg Baum wrote:
>> PhilipPirrip wrote:
>>
>>> Why does \input@path end with two slashes, as in
>>> /home/user/directory//
>>
>> IIRC this means that also sub directories are searched, but this should
>> be documented in some TeX or LaTeX docs.
I
Why does \input@path end with two slashes, as in
/home/user/directory//
IIRC this means that also sub directories are searched, but this should
be documented in some TeX or LaTeX docs.
Not sure how it all works for (La)TeX, I'm assuming this is all handled
by the OS. Unixoids (OSX, Linux)
On 08/19/2015 04:44 PM, Georg Baum wrote:
PhilipPirrip wrote:
Why does \input@path end with two slashes, as in
/home/user/directory//
IIRC this means that also sub directories are searched, but this should be
documented in some TeX or LaTeX docs.
and why is its output
/home/user/dir
On 08/19/2015 04:44 PM, Georg Baum wrote:
PhilipPirrip wrote:
Why does \input@path end with two slashes, as in
/home/user/directory//
IIRC this means that also sub directories are searched, but this should be
documented in some TeX or LaTeX docs.
and why is its output
"/home/user/dir
PhilipPirrip wrote:
Why does \input@path end with two slashes, as in
/home/user/directory//
IIRC this means that also sub directories are searched, but this should be
documented in some TeX or LaTeX docs.
and why is its output
/home/user/dir ectory//
(note quotation marks, and two
PhilipPirrip wrote:
> Why does \input@path end with two slashes, as in
> /home/user/directory//
IIRC this means that also sub directories are searched, but this should be
documented in some TeX or LaTeX docs.
> and why is its output
> "/home/user/dir ectory/"/
> (note quotation marks, and two
Did a little research. \input@path is in src/Buffer.cpp, but since 2.0.1
another method has been introduced /see below/.
It, however, doesn't seem to work for biber, no .bib files are found.
So, any idea why \input@path exports, or should export
{/home/user/dir ecto ry/}
instead of simple
Did a little research. \input@path is in src/Buffer.cpp, but since 2.0.1
another method has been introduced /see below/.
It, however, doesn't seem to work for biber, no .bib files are found.
So, any idea why \input@path exports, or should export
{"/home/user/dir ecto ry"/}
instead of simple
Why does \input@path end with two slashes, as in
/home/user/directory//
and why is its output
/home/user/dir ectory//
(note quotation marks, and two separate ending slashes) when the folder
name contains spaces?
Why does \input@path end with two slashes, as in
/home/user/directory//
and why is its output
"/home/user/dir ectory/"/
(note quotation marks, and two separate ending slashes) when the folder
name contains spaces?
17 matches
Mail list logo
