Relative paths with windows path separator does not work in TeXlive2019.
zdenek.wagner at gmail.com
Fri Jul 26 14:46:14 CEST 2019
Really? In Windows a colon separates a drive letter hence it must not
be used as the separator in TEXINPUT. I do not have Windows with TeX
so I cannot try but at least emTeX for OS/2 and MS-DOS used
I understand your requirement for freedom for users. Usage of `cd` is
not against freedom. I allow users to call the script (supplied by me)
in any way they like. I do `cd` inside the script and when the script
terminates, the user is back in the same directory from which the
script was started. The user need not know what's going on behind the
scene, the user only wishes that it works as expected.
pá 26. 7. 2019 v 13:54 odesílatel Kirill Balunov
<kirillbalunov at gmail.com> napsal:
> Paul thanks! It works to some extent, though again it uses the specifics of windows:)) As suggested in this answer https://tex.stackexchange.com/a/403973/181328 on windows you need to use a `;` (semicolon) instead of a `:` (colon). But this works.
> with kind regards,
> пт, 26 июл. 2019 г. в 13:02, Paul Gessler <pdgessler at gmail.com>:
>> I do not have a Windows machine to hand to test, but would adding your
>> input file's path to the TEXINPUTS environment variable suffice for
>> your use case? Only do this when you need to find files with this type
>> of path specification, not in general. I _think_ it will do what
>> you're after, without needing to add another command line option. I
>> could be wrong (please someone tell me/Kirill if so).
>> On Fri, 26 Jul 2019 at 04:33, Kirill Balunov <kirillbalunov at gmail.com> wrote:
>> > Hmm, thanks again. It is clear that everything is not easy with this option. Then what do you think about the additional option `-input-directory=` that will also be as good as `-output-directory=`? Or do you think this is an overkill for this?
>> > with kind regards,
>> > -gdg
More information about the tex-live