[OS X TeX] repetition in compiling

[Herbert Schulz]

> On Aug 2, 2021, at 2:24 PM, Nitecki, Zbigniew H. <Zbigniew.Nitecki at tufts.edu> wrote:
> 
> I am experiencing a strange phenomenon which I am not sure I can replicate in a minimal example.  Has anyone else experienced this?
> 
> I am working on a book-length project using the memoir documentclass and using a master file with \input statements for different sections, which are in separate files.
> Today, I had written a brief \subsection, compiled the whole book with that, decided to change it, made changes and wrote a subsequent subsection, and compiled again.
> The intial subsection showed up twice—in the proper place, and followed by (one copy of) the subsequent subsection.
> I commented out all that material in the source file (there is only one copy of either subsection there) and compiled twice, hoping to shut off whatever was leading to the
> loop that repeats the subsection.  As desired, neither subsection appeared.
> So then I uncommented the two subsections, and compiled.  Again, I got two copies of (only) the initial section.
> Then I copied the previously uncommented material into a new file, modified my master file to input the new file in place of the (whole chapter) file where this material had 
> appeared.  This time the initial subsection showed up three times (again followed by the succeeding section, in a single copy).
> Then I went back to my original setup (ie, took out the \input for the test file, but replaced the \input for the whole chapter.
> Now that also compiles with three copies of the offending subsection.
> 
> Needless to say, I will erase the two subsections and retype everything from scratch, but I am curious about what could possibly be causing what is clearly some kind of 
> “do loop” that the compiler is getting from my source file.
> 
> I experienced a similar issue several years ago with another book project, but did my workaround without pursuing an investigation of why it happened.
> 
> 
> 
> Zbigniew Nitecki

Howdy,

This sounds really strange. Could you have a file naming convention that could be going awry? Can you make a minimal example that demonstrates the problem?

Good Luck,

Herb Schulz
herbs at wideopenwest.com