David Carlisle wrote:
> try a file without \end[document} (\end for you:-) and type \end to the *
> prompt
> you will see that the text such as
> --output-directory=...
> after the filename is just typeset
True -- I had not considered that possibility.
> The problem is that if you configure
Phil,
> E:\TeX\Projects\WBH\Welcome>xetex foo --output-directory=../dynamic-
content
> (./foo.tex This is the intended foo.tex )
isn't that just because the flags after the filename are ignored?
Personally I'd just add it to the end of the list of reasons never to use
--output-directory,
Zdeněk Wagner napsal :
> I have just tried on Linux and found that it depends on the way how
> the file name is specified, namely whether foo.tex is given including
> the extension or only foo:
Under Windows (7, Ultimate, 64-bit) what appears to matter is the order of
parameter v. qualifier;
I have just tried on Linux and found that it depends on the way how the
file name is specified, namely whether foo.tex is given including the
extension or only foo:
$ xetex --output-directory=./dynamic-content foo
This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016) (preloaded
If XeTeX is invoked on file foo.tex specifying
--output-directory=../dynamic-content,
and if there is also a file ../dynamic-content/foo.tex, then XeTeX will process
that file
rather than the file which it was instructed to process :
> \message {This is the intended foo.tex}
> \end
> This is
