Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Philip Taylor]

Zdeněk Wagner wrote:

>> [PT] What are "the normalisation rules", Zdeněk ? ** Phil.

> A path can be specified by many equivalent ways, for instance a/./b
> is the same as a/b, a/c/../b is again a/b (it need not be true in
> unix systems). Doble slashes are ignored too, a//b is again a/b. The
> canonical path does not contain double slashes, ./, ../, the engine
> may remove them before searching the file.

Hmmm, thank you : however, it would appear to be the case (here, at least) that 
"//" <> "/" :

> E:\TeX\Projects\WBH\Welcome>xetex
> --output-directory=../dynamic-content /foo.tex This is XeTeX, Version
> 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX) (preloaded
> format=xetex) restricted \write18 enabled. entering extended mode 
> (/foo.tex This is the intended foo.tex) *\end No pages of output. 
> Transcript written on ../dynamic-content/foo.log.
> 
> E:\TeX\Projects\WBH\Welcome>xetex
> --output-directory=../dynamic-content //foo.tex This is XeTeX,
> Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX) (preloaded
> format=xetex) restricted \write18 enabled. entering extended mode ! I
> can't find file `//foo.tex'.

** Phil.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Zdenek Wagner]

2017-01-15 21:05 GMT+01:00 Philip Taylor :

>
>
> Zdenek Wagner wrote:
>
> > No, ./ is not a path specification, the normalization rules will
> > remove it, ./foo.tex is the same as foo.tex. If you want to specify
> > the path, ../Welcome/foo.tex will help because such a file is not
> > below dynamic-content.
>
> What are "the normalisation rules", Zdeněk ?
> ** Phil.
>

A path can be specified by many equivalent ways, for instance a/./b is the
same as a/b, a/c/../b is again a/b (it need not be true in unix systems).
Doble slashes are ignored too, a//b is again a/b. The canonical path does
not contain double slashes, ./, ../, the engine may remove them before
searching the file.


Zdeněk Wagner
http://ttsm.icpf.cas.cz/team/wagner.shtml
http://icebearsoft.euweb.cz


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Philip Taylor]

Zdenek Wagner wrote:

If you want to specify the path, ../Welcome/foo.tex will help because such a 
file is not below dynamic-content.

That would indeed appear to be the case, Zdeněk :

> E:\TeX\Projects\WBH\Welcome>xetex --output-directory=../dynamic-content 
> ../welcome/foo.tex
> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX) 
> (preloaded format=xetex)
>  restricted \write18 enabled.
> entering extended mode
> (../dynamic-content/../Welcome/foo.tex This is the intended foo.tex
> (e:/TeX/Projects/WBH/Welcome/foo.aux This is the intended foo.aux) )
> No pages of output.
> Transcript written on ../dynamic-content/foo.log.
> 
> E:\TeX\Projects\WBH\Welcome>

but is not the path through which it finally located the intended "foo.tex" 
more than a little arcane ?

> (../dynamic-content/../Welcome/foo.tex This is the intended foo.tex ...)

** Phil.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Philip Taylor]

Zdenek Wagner wrote:

> No, ./ is not a path specification, the normalization rules will
> remove it, ./foo.tex is the same as foo.tex. If you want to specify
> the path, ../Welcome/foo.tex will help because such a file is not
> below dynamic-content.

What are "the normalisation rules", Zdeněk ?
** Phil.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Zdenek Wagner]

No, ./ is not a path specification, the normalization rules will remove it,
./foo.tex is the same as foo.tex. If you want to specify the path,
../Welcome/foo.tex will help because such a file is not below
dynamic-content.

Zdeněk Wagner
http://ttsm.icpf.cas.cz/team/wagner.shtml
http://icebearsoft.euweb.cz

2017-01-15 20:26 GMT+01:00 Philip Taylor :

>
>
> Philip Taylor wrote:
>
> > But the defined behaviour for :
> >
> >   o xetex --output-directory=../dynamic-content
> E:/TeX/Projects/WBH/Welcome/foo.tex
> >
> > must /surely/ be to process E:/TeX/Projects/WBH/Welcome/foo.tex, not
> E:/TeX/Projects/WBH/Dynamic-content/foo.tex, which is what it does;
>
> This statement was in error :
>
> >   o xetex --output-directory=../dynamic-content
> E:/TeX/Projects/WBH/Welcome/foo.tex
>
> does indeed process E:/TeX/Projects/WBH/Welcome/foo.tex as requested.
> Yet with
> the current working directory :
>
> > E:/TeX/Projects/WBH/Welcome/foo.tex
>
> >   o xetex --output-directory=../dynamic-content ./foo.tex
>
> the file that is actually processed is
>
> > E:/TeX/Projects/WBH/Dynamic-content/foo.tex
>
> In both cases, the path to the source directory has been specified, yet
> "E:/TeX/Projects/WBH/Welcome/" is correctly honoured while "./" (for . =
> E:/TeX/Projects/WBH/Welcome) is not.  I remain completely confused by this
> seemingly aberrant and inconsistency behaviour.
>
> Philip Taylor
> 
> E:\TeX\Projects\WBH\Welcome>xetex --output-directory=../dynamic-content
> E:/TeX/Projects/WBH/Welcome/foo.tex
> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX)
> (preloaded format=xetex)
>  restricted \write18 enabled.
> entering extended mode
> (e:/TeX/Projects/WBH/Welcome/foo.tex This is the intended foo.tex
> (e:/TeX/Projects/WBH/Welcome/foo.aux This is the intended foo.aux) )
> No pages of output.
> Transcript written on ../dynamic-content/foo.log.
>
> E:\TeX\Projects\WBH\Welcome>xetex --output-directory=../dynamic-content
> ./foo.tex
> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX)
> (preloaded format=xetex)
>  restricted \write18 enabled.
> entering extended mode
> (../dynamic-content/./foo.tex This is the unintended foo.tex
> (e:/TeX/Projects/WBH/Welcome/foo.aux This is the intended foo.aux) )
> No pages of output.
> Transcript written on ../dynamic-content/foo.log.
>
> E:\TeX\Projects\WBH\Welcome>
>


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Philip Taylor]

Philip Taylor wrote:

> But the defined behaviour for :
> 
>   o xetex --output-directory=../dynamic-content 
> E:/TeX/Projects/WBH/Welcome/foo.tex
> 
> must /surely/ be to process E:/TeX/Projects/WBH/Welcome/foo.tex, not 
> E:/TeX/Projects/WBH/Dynamic-content/foo.tex, which is what it does; 

This statement was in error :

>   o xetex --output-directory=../dynamic-content 
> E:/TeX/Projects/WBH/Welcome/foo.tex

does indeed process E:/TeX/Projects/WBH/Welcome/foo.tex as requested.  Yet with
the current working directory :

> E:/TeX/Projects/WBH/Welcome/foo.tex

>   o xetex --output-directory=../dynamic-content ./foo.tex

the file that is actually processed is 

> E:/TeX/Projects/WBH/Dynamic-content/foo.tex

In both cases, the path to the source directory has been specified, yet 
"E:/TeX/Projects/WBH/Welcome/" is correctly honoured while "./" (for . = 
E:/TeX/Projects/WBH/Welcome) is not.  I remain completely confused by this 
seemingly aberrant and inconsistency behaviour. 

Philip Taylor

E:\TeX\Projects\WBH\Welcome>xetex --output-directory=../dynamic-content 
E:/TeX/Projects/WBH/Welcome/foo.tex
This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX) (preloaded 
format=xetex)
 restricted \write18 enabled.
entering extended mode
(e:/TeX/Projects/WBH/Welcome/foo.tex This is the intended foo.tex
(e:/TeX/Projects/WBH/Welcome/foo.aux This is the intended foo.aux) )
No pages of output.
Transcript written on ../dynamic-content/foo.log.

E:\TeX\Projects\WBH\Welcome>xetex --output-directory=../dynamic-content 
./foo.tex
This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX) (preloaded 
format=xetex)
 restricted \write18 enabled.
entering extended mode
(../dynamic-content/./foo.tex This is the unintended foo.tex
(e:/TeX/Projects/WBH/Welcome/foo.aux This is the intended foo.aux) )
No pages of output.
Transcript written on ../dynamic-content/foo.log.

E:\TeX\Projects\WBH\Welcome>


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[mskala]

On Sun, 15 Jan 2017, David Carlisle wrote:
>    Specify the directory dirname to which output files are
> written. Also look for
>    input files in dirname first, before looking along the normal
> search path. See
>    Section 3.4 [Output file location], page 9.

The general principle here is that TeX expects to modify files in place.
Stuff like the multi-stage compilation of LaTeX implicitly assumes that it
works this way, but it is TeX, not LaTeX, that originally instituted the
concept.  It's not in keeping with the Unix philosophy of programs working
as pipes, and it causes trouble for people with other expectations.  For
instance, I nearly always run TeX engines through Makefiles, and the
rewriting of files that are used as both input and output screws up how
Make works and requires complicated side handling.  But the "modify in
place" philosophy is built into TeX at a very deep level; it's not going
to change soon; and it's probably pointless to expect that it could be
turned off in a real way by a simple command line option.

-- 
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.bc.ca/

--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Philip Taylor]

Ulrike Fischer wrote:

> The output-directory is not only for output-files. XeTeX must also be
> able to read from this folder, e.g. a toc-file or an aux-file. And if
> there is (in a latex compilation) an (older) foo.aux in the current
> folder and a new foo.aux in /dynamic-content you would want it to
> find the newer one. 

Whether or not the file "foo.aux" in ../dynamic-content is newer,
it should be read in preference to the one in the current directory
because that is the defined behaviour when --output-directory=../dynamic-content

But the defined behaviour for :

o xetex --output-directory=../dynamic-content 
E:/TeX/Projects/WBH/Welcome/foo.tex

must /surely/ be to process E:/TeX/Projects/WBH/Welcome/foo.tex, not 
E:/TeX/Projects/WBH/Dynamic-content/foo.tex, which is what it does; the 
"texinputs" path does not come into this, since
an explicit directory has been given.  Furthermore, if both 
E:/TeX/Projects/WBH/Welcome/foo.tex 
and E:/TeX/Projects/WBH/Dynamic-content/foo.tex contain "\input 
E:/TeX/Projects/WBH/Welcome/foo.aux", then E:/TeX/Projects/WBH/Welcome/foo.aux 
is indeed \input as specified (i.e., the value of "texinputs" is ignored (as it 
should be) because an explicit path to the file has been given).

Philip Taylor


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[David Carlisle]

On 15 January 2017 at 09:20, Philip Taylor  wrote:

>
>
> But all of this is besides the point :  surely
>
> o XeTeX --output-directory=../dynamic-content foo (or foo.tex)
>
> should compile foo.tex, not ../dynamic-content/foo.tex
>
> ** Phil.
>


No I think not,  if you do not give a full path to a file tex (usually)
looks in . first
then looks along the path. --output-directory --output-directory is
documented
as using the specified directory before the path

texdoc web2c page 8 says

`-output-directory=dirname'
   Specify the directory dirname to which output files are
written. Also look for
   input files in dirname first, before looking along the
normal search path. See
   Section 3.4 [Output file location], page 9.


but as I said this thread just joins the many previous ones, it seems like
anyone who
uses --output-directory eventually asks about some confusing aspect of its
behaviour.

I don't think it would be better here if tex looked in the current
directory, then the output
directory then the path, as that would mean that if you add
-output-directory a document
would keep inputting stale tables of contents and aux files from the
current directory
not new ones being written elsewhere.

You can always use a full path to the input file to specify a specific file.

David


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Ulrike Fischer]

Am Sun, 15 Jan 2017 09:20:13 + schrieb Philip Taylor:

> But all of this is besides the point :  surely 
> 
>   o XeTeX --output-directory=../dynamic-content foo (or foo.tex)
> 
> should compile foo.tex, not ../dynamic-content/foo.tex

The output-directory is not only for output-files. XeTeX must also
be able to read from this folder, e.g. a toc-file or an aux-file.
And if there is (in a latex compilation) an (older) foo.aux in the
current folder and a new foo.aux in /dynamic-content you would want
it to find the newer one. Which means that the output-directory must
be added at the begin of the texinputs path.  
(In miktex it is the other way round and this can be quite confusing
when I test something with output-directory)

On the whole I would say, that if you want to use --output-directory
you should avoid files with the same name in both folder. Like the
other adjustments one should do it doesn't take to much brain-power
to follow such a rule. 


-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Zdenek Wagner]

2017-01-15 16:00 GMT+01:00 Philip Taylor :

>
>
> Zdeněk Wagner wrote:
>
> > The same on Linux but with the full (absolute) path it works as
> > expected:
> >
> > [zw@. tmp]$ xetex --output-directory=./dynamic-content /tmp/foo.tex
>
> But from "/tmp", does "./dynamic-content" exist, and if so, does it
> contain an instance of "foo.tex" ?
>

Yes, it does, I have both /tmp/foo.tex and /tmp/dynamic-content/foo.tex and
both are different.

>
> ** Phil.
>



Zdeněk Wagner
http://ttsm.icpf.cas.cz/team/wagner.shtml
http://icebearsoft.euweb.cz


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Philip Taylor]

Zdeněk Wagner wrote:

> The same on Linux but with the full (absolute) path it works as
> expected:
> 
> [zw@. tmp]$ xetex --output-directory=./dynamic-content /tmp/foo.tex

But from "/tmp", does "./dynamic-content" exist, and if so, does it contain an 
instance of "foo.tex" ?

** Phil.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Zdenek Wagner]

The same on Linux but with the full (absolute) path it works as expected:

[zw@. tmp]$ xetex --output-directory=./dynamic-content /tmp/foo.tex
This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016) (preloaded
format=xetex)
entering extended mode
(/tmp/foo.tex [1] )
Output written on ./dynamic-content/foo.pdf (1 page).
Transcript written on ./dynamic-content/foo.log.

My ADSL speed is 8 Mbps for download but only 512 kbps for upload, so
syncing large files is a problem (uploading 1 hour video takes almost a
week). I use a different strategy for my work, I take advantage of
versioning and use either subversion or git. Only the source files that
cannot be generated are versioned. My hard disk certainly will not die
within a few hours (in fact not within a few months) and I commit
frequently and at least daily push the git cloned repository. If you do not
share the work with others but want to have it available from several
computers, Dropbox can be used as a siple subresion and/or git server. The
only rule to surviv is: do not do "svn commit" or "git push" if you are
offline. And if you do, do not work on other computer before connecting the
computer with the latest repository version and syncing it.



Zdeněk Wagner
http://ttsm.icpf.cas.cz/team/wagner.shtml
http://icebearsoft.euweb.cz

2017-01-15 10:26 GMT+01:00 Philip Taylor :

>
>
> Philip Taylor wrote:
>
> > But all of this is besides the point :  surely
> >
> >   o XeTeX --output-directory=../dynamic-content foo (or foo.tex)
> >
> > should compile foo.tex, not ../dynamic-content/foo.tex
>
> Note that this occurs even if a specific path to "foo.tex" is given :
>
> > E:\TeX\Projects\WBH\Welcome>xetex --output-directory=../dynamic-content
> ./foo
> > This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX)
> (preloaded format=xetex)
> >  restricted \write18 enabled.
> > entering extended mode
> > (../dynamic-content/./foo.tex This is the unintended foo.tex)
> > *\end
> > No pages of output.
> > Transcript written on ../dynamic-content/foo.log.
> >
> > E:\TeX\Projects\WBH\Welcome>xetex --output-directory=../dynamic-content
> ./foo.tex
> > This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX)
> (preloaded format=xetex)
> >  restricted \write18 enabled.
> > entering extended mode
> > (../dynamic-content/./foo.tex This is the unintended foo.tex)
> > *\end
> > No pages of output.
> > Transcript written on ../dynamic-content/foo.log.
> >
> > E:\TeX\Projects\WBH\Welcome>
>


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Philip Taylor]

Philip Taylor wrote:

> But all of this is besides the point :  surely 
> 
>   o XeTeX --output-directory=../dynamic-content foo (or foo.tex)
> 
> should compile foo.tex, not ../dynamic-content/foo.tex

Note that this occurs even if a specific path to "foo.tex" is given :

> E:\TeX\Projects\WBH\Welcome>xetex --output-directory=../dynamic-content ./foo
> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX) 
> (preloaded format=xetex)
>  restricted \write18 enabled.
> entering extended mode
> (../dynamic-content/./foo.tex This is the unintended foo.tex)
> *\end
> No pages of output.
> Transcript written on ../dynamic-content/foo.log.
> 
> E:\TeX\Projects\WBH\Welcome>xetex --output-directory=../dynamic-content 
> ./foo.tex
> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX) 
> (preloaded format=xetex)
>  restricted \write18 enabled.
> entering extended mode
> (../dynamic-content/./foo.tex This is the unintended foo.tex)
> *\end
> No pages of output.
> Transcript written on ../dynamic-content/foo.log.
> 
> E:\TeX\Projects\WBH\Welcome>


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Philip Taylor]

Dominik Wujastyk wrote:

> ​I routinely work on tex projects in my Dropbox file area. I mean
> every day, all the time.  I've never noticed a problem with Dropbox
> mirroring my ephemeral files, even the synctex one.  I have
> moderately fast wifi at home and fast ethernet at work; it might be
> different if the bandwidth was low and slow.  The little dropbox icon
> shows that my files are updated more or less instantly.  I honestly
> have never noticed any overhead.

On a 3Mbps link, Dominik, synching (e.g.,) the Descriptive Catalogue
of Greek MSS in the Lambeth Palace Library ties up my link for hours
at a time following each compilation.  I therefore need to exclude
the generated PDF from synchronisation, and as there is no way of which
I am aware to send the PDF to anywhere other than the same location as
the (relatively trivial) auxiliary files, I send them all to a location
for which Dropbox synchronisation is inhibited.

But all of this is besides the point :  surely 

o XeTeX --output-directory=../dynamic-content foo (or foo.tex)

should compile foo.tex, not ../dynamic-content/foo.tex

** Phil.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Dominik Wujastyk]

On 14 January 2017 at 10:39, Philip Taylor  wrote:

> ​...​
>
> If (as I do) one uses Dropbox to mirror one's work for security, the last
> thing one needs is for Dropbox to continually synch one's ephemeral files
> (.aux, .log, .ind/idx, .pdf, etc), whence my unvarying use of
> --output-directory via TeXworks configuration options.
>
> ** Phil.
>
>
​I routinely work on tex projects in my Dropbox file area. I mean every
day, all the time.  I've never noticed a problem with Dropbox mirroring my
ephemeral files, even the synctex one.  I have moderately fast wifi at home
and fast ethernet at work; it might be different if the bandwidth was low
and slow.  The little dropbox icon shows that my files are updated more or
less instantly.  I honestly have never noticed any overhead.

Best,
Dominik


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Philip Taylor]

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 tex to write somewhere strange you have 
> to configure _everything_
> (makeindex, bibtex, tex, ... to find the files that have been written: it 
> causes endless confusion and questions
> on support lists) 

Well, as soon as I started using --output-directory, I adjusted my methodology 
to automatically
search for such files in the appropriate place; it didn't seem to require a 
great deal of brain-
power ...

> compared to just (for example) configuring your editor to save a copy to your 
> dropbox
> backup folder on each save.

I have no idea whether TeXworks can do that, but for me --output-directory is a 
very useful feature.
** Phil.


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[David Carlisle]

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,
although that list is so long, it's hard to find the end:-)

David


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Philip Taylor]

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;
the presence or absence of the file extension appears to matter not :

> E:\TeX\Projects\WBH\Welcome>xetex --output-directory=../dynamic-content foo
> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX) 
> (preloaded format=xetex)
>  restricted \write18 enabled.
> entering extended mode
> (../dynamic-content/./foo.tex This is the unintended foo.tex )
> No pages of output.
> Transcript written on ../dynamic-content/foo.log.
> 
> E:\TeX\Projects\WBH\Welcome>xetex --output-directory=../dynamic-content 
> foo.tex
> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX) 
> (preloaded format=xetex)
>  restricted \write18 enabled.
> entering extended mode
> (../dynamic-content/./foo.tex This is the unintended foo.tex )
> No pages of output.
> Transcript written on ../dynamic-content/foo.log.
> 
> E:\TeX\Projects\WBH\Welcome>xetex foo.tex 
> --output-directory=../dynamic-content
> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX) 
> (preloaded format=xetex)
>  restricted \write18 enabled.
> entering extended mode
> (./foo.tex This is the intended foo.tex )
> No pages of output.
> Transcript written on foo.log.
> 
> E:\TeX\Projects\WBH\Welcome>xetex foo --output-directory=../dynamic-content
> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX) 
> (preloaded format=xetex)
>  restricted \write18 enabled.
> entering extended mode
> (./foo.tex This is the intended foo.tex )
> No pages of output.
> Transcript written on foo.log.
-- 
Philip Taylor


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] [tex-live] Problem with XeTeX's (and perhaps other binaries -- not investigated) handling of --output-directory

[Zdenek Wagner]

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
format=xetex)
entering extended
mode

(./foo.tex [1]
)

Output written on ./dynamic-content/foo.pdf (1 page).

$ xetex --output-directory=./dynamic-content foo.tex
This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016) (preloaded
format=xetex)
entering extended
mode

(./dynamic-content/foo.tex [1]
)

Output written on ./dynamic-content/foo.pdf (1 page).

I have also tried luatex, tex, and pdfcsplain and all of them behave
identically.



Zdeněk Wagner
http://ttsm.icpf.cas.cz/team/wagner.shtml
http://icebearsoft.euweb.cz

2017-01-14 15:41 GMT+01:00 Philip Taylor :

> 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 XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX)
> (preloaded format=xetex)
> >  restricted \write18 enabled.
> > entering extended mode
> > (../dynamic-content/./foo.tex This is the unintended foo.tex )
> > No pages of output.
> > Transcript written on ../dynamic-content/foo.log.
>
> --
>
> Philip Taylor
>


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex