Re: UNC paths in TeX

Jan already answered this question (and provided a pointer to the documentation), but for completeness' sake... On Mon, 5 Jan 2004, Sam Steingold wrote: > > * Igor Pechtchanski <[EMAIL PROTECTED]> [2004-01-05 16:28:16 -0500]: > > > > On Mon, 5 Jan 2004, Sam Steingold wrote: > > > >> It appears th

Re: UNC paths in TeX

> * Igor Pechtchanski <[EMAIL PROTECTED]> [2004-01-05 16:28:16 -0500]: > > On Mon, 5 Jan 2004, Sam Steingold wrote: > >> It appears that TeX does not support UNC paths while ls does. > Which TeX? tetex-2.0.2-13. >> This is strange (I expected that to be handled transparently by the dll) > > Some

Re: UNC paths in TeX

Igor Pechtchanski writes: >> It appears that TeX does not support UNC paths while ls does. >> This is strange (I expected that to be handled transparently by the dll) This was disabled by default, as it clashes with the usage of '//' by kpathsea, and you can easily work around it, as you show. Y

Re: UNC paths in TeX

On Mon, Jan 05, 2004 at 04:10:02PM -0500, Sam Steingold wrote: >It appears that TeX does not support UNC paths while ls does. >This is strange (I expected that to be handled transparently by the dll) > >$ TEXINPUTS=//host/path:.: pdflatex gdm.tex > >! LaTeX Error: File `oubraces.sty' not found.

Re: UNC paths in TeX

On Mon, 5 Jan 2004, Sam Steingold wrote: > It appears that TeX does not support UNC paths while ls does. Which TeX? > This is strange (I expected that to be handled transparently by the dll) Some applications "optimize" two leading slashes into one slash. This happens before the Cygwin DLL has

UNC paths in TeX

It appears that TeX does not support UNC paths while ls does. This is strange (I expected that to be handled transparently by the dll) $ TEXINPUTS=//host/path:.: pdflatex gdm.tex ! LaTeX Error: File `oubraces.sty' not found. ... $ TEXINPUTS=/cygdrive/x/path:.: pdflatex gdm.tex fine $ ls //hos