[tex-live] Bug in TexLive 2005 and 2007? Non-writable aux-file

George N. White III gnwiii at gmail.com
Sat Mar 10 23:33:20 CET 2007

On 3/10/07, David Kastrup <dak at gnu.org> wrote:

> Reinhard Kotucha <reinhard.kotucha at web.de> writes:
> >>>>>> "Taco" == Taco Hoekwater <taco at elvenkind.com> writes:
> >
> >   > Somebody on tex-implementors suggested an Abort/Retry/Fail
> >   > approach like DOS used to have, and that makes sense to
> >   > me. Definately on Windows, but I would like to have that as well
> >   > (and I am on linux).

Whatever is decided, it should be the same across platforms.

> > The real problem is that the name of the output file is changed
> > silently unless a new name is provided.  If this can be fixed, you can
> > press <return> as often as you want.  You will remain in the loop
> > as long as tex can not access the file and tex will proceed when the
> > file is accessible.
> >
> > An easy way to abort would be nice, for instance, let tex abort
> > immediately when CTRL-C is pressed while tex is waiting for input
> > from the keyboard.

Most users (the ones who don't try C-Alt+Del) click on the little 'x'
in such situations.

> That makes pressing C-c a matter of timing: if you press it while TeX
> is busy (in order to get control back and check where you are), and
> TeX manages to get to the input prompt just before you actually press
> C-c, the process will get terminated accidentally.
> So I think that pressing C-c twice should be required for termination.

When the system bogs down, people tend to press C-c multiple times,
then Alt-F4, then C-Alt+Del.

What if C-c once gets you to a prompt that just loops on additional C-c?
If C-c could discard any buffered inputs you could be more certain you
are seeing the response to a prompt and not someone's cat walking on
the keyboard.

George N. White III <aa056 at chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia

More information about the tex-live mailing list