[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-AUCTeX] Re: 11.82; TeX-master not used after TeX-next-error

From: David Kastrup
Subject: Re: [Bug-AUCTeX] Re: 11.82; TeX-master not used after TeX-next-error
Date: Mon, 20 Feb 2006 11:57:39 +0100
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

Ralf Angeli <address@hidden> writes:

> * David Kastrup (2006-02-19) writes:
>> Ralf Angeli <address@hidden> writes:
>>> Because `TeX-command-buffer' will point to the original file and not
>>> to the region file after e.g. LaTeX was run with `C-c C-r'.
>>> `(TeX-active-master)', however, will return the region file.
>> Uh, so what?  You can always use
>> (with-current-buffer TeX-command-buffer (TeX-active-master))
>> in case you need the master.
> D'oh.  I'll tell you when I'm done bashing my head against the table
> plate.
> Anyway, an easy fix for the reported problem would be the following
> patch:
> The normalization of strings for comparison destroys some information
> which might be relevant, but maybe it is better than messing around
> with `TeX-command-buffer'.  I'll have to look deeper into what
> functions would have to be changed if we use the latter, but as far as
> I can already see it would be at least `TeX-active-buffer' besides
> `TeX-next-error'.

What we _currently_ do is "messing around", namely with `TeX-master'.
Using `TeX-command-buffer' would just read-access variables.  And the
current variant causes several strange hickups and unexpected things
to happen semi-permanently.  If the user explicitly set TeX-master by
file variable or C-c C-_, it is a reasonable expectation that AUCTeX
will not mess with that setting.

Although I am responsible for the current `TeX-next-error' behaviour,
I think it might have been quite the wrong fix for the encountered

David Kastrup, Kriemhildstr. 15, 44793 Bochum

reply via email to

[Prev in Thread] Current Thread [Next in Thread]