ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
Cc: patrick@gundla.ch
Subject: Re: Re: TeX run : 8
Date: Wed, 2 Mar 2005 21:39:21 +0100	[thread overview]
Message-ID: <a06210210be4bd0b38876@[62.134.72.151]> (raw)

Hi Patrick,



Patrick Gundlach <patrick@gundla.ch> wrote:

>  Hello again,
>
>  > I have tried your small file (the one you have sent me) an a vanilla
>  > tetex 3.0 and an older texlive (I had to dig out my iBook -- anybody
>  > wants to buy a used iBook?) and both were two runs.
>
>  Ah, not so fast, Patrick. I can reproduce your problem:
>
>  $ ls -lR
>  .:
>  total 4
>  drwxr-xr-x    4 pg       pg            136 Mar  2 20:27 PARTS
>  -rw-r--r--    1 pg       pg            117 Mar  2 20:28 TEST.tex
>
>  ./PARTS:
>  total 8
>  -rw-r--r--    1 pg       pg             40 Mar  2 20:27 ONE.tex
>  -rw-r--r--    1 pg       pg             40 Mar  2 20:27 TWO.tex
>
>  (so setup is TEST.tex in all capitals and ONE.tex and TWO.tex in
>  subdir, tetex 3.0). Now I run
>
>  texexec --pdf test.tex
>
>  (lowercase test.tex !)
>
>  and I get:
>
>  [...]
>
>   utility file analysis : another run needed
>                 TeX run : 8
>
>
>  [...]
>
>
>  Note that the standard OS X filesystem is case preserving, but not
>  case sensitive when accessing a file. So accessing test.tex would be
>  happy with a file called TEST.tex. It is possible to create a pure
>  case sensitive HFS+ filesystem, but it isn't necessary to reproduce
>  the problem. (It would probably avoid it, though).
>
>
>  Patrick



So I made a new setup:
new files/folders and every names lowercase (folders, files, references).

The first time I executed
texexec --pdf test.tex
it looked good: 2 runs!
Then I executed
texexec --pdf test.tex
once more and now it was 8 runs again!

Does this make sense?

Steffen

             reply	other threads:[~2005-03-02 20:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02 20:39 Steffen Wolfrum [this message]
2005-03-02 20:56 ` Patrick Gundlach
2005-03-02 23:18   ` Hans Hagen
2005-03-03 10:34     ` Patrick Gundlach
2005-03-03 11:52       ` Hans Hagen
2005-03-03 12:33         ` Patrick Gundlach
2005-03-03 13:08           ` Hans Hagen
2005-03-03 11:07     ` Patrick Gundlach
2005-03-03 11:16       ` Taco Hoekwater
2005-03-03 11:17       ` Patrick Gundlach
2005-03-03 11:59       ` Hans Hagen
2005-03-03 21:54         ` Angus Lees
2005-03-04 11:37         ` Re[2]: " Giuseppe Bilotta
2005-03-04 12:14           ` Taco Hoekwater
2005-03-07 18:53             ` Peter Münster
2005-03-08 18:24               ` Patrick Gundlach
2005-03-08 20:33                 ` Peter Münster
  -- strict thread matches above, loose matches on Subject: below --
2005-03-11 11:07 Steffen Wolfrum
2005-03-03 13:40 Steffen Wolfrum
2005-03-03 10:05 Patrick Gundlach
2005-03-03 10:34 ` Adam Lindsay
2005-03-02 11:59 Re: [OS X TeX] " Steffen Wolfrum
2005-03-02 12:31 ` Hans Hagen
2005-03-02 19:46   ` Patrick Gundlach
2005-03-02 20:05     ` Patrick Gundlach
2005-03-02 20:32       ` Hans Hagen
2005-03-02 23:32     ` Adam Lindsay
2005-03-03  7:38       ` Hans Hagen
2005-03-03  9:49         ` Adam Lindsay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='a06210210be4bd0b38876@[62.134.72.151]' \
    --to=context@st.estfiles.de \
    --cc=ntg-context@ntg.nl \
    --cc=patrick@gundla.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).