Re: (non-bug) lilypond-book & secondary source files

Cameron Crowe via bug-lilypond <[email protected]> writes:

> Just a thought--not a bug.
>
> lilypond-book refuses to overwrite a main source file, but happily
> overwrites secondary source files included into the main source
> file. Irritating if you use the .tex extension for included chapters
> of a musicological document and even just accidentally call
> lilypond-book without specifying a separate output dir.
>
> "Don't do that." and "Version control!" would be perfectly good
> responses,

Version control is not a substitute for backups.

> and I probably have a few other minor (shrug-worth?) points if there
> is interest in hearing them.

Just anecdotally: on MSDOS file systems, writing a file whatever.tex.aux
was equivalent to writing a file whatever.tex and when writing
\include{something} in a LaTeX file, this caused a file something.aux to
be created/written.

This made the punishment for writing \include{something.tex} instead of
the correct \include{something} pretty severe (until MikTeX was made to
detect this special case and refuse the operation).

-- 
David Kastrup