Re: next-error-last-buffer

[Ted Zlatanov]

On 28 May 2004, address@hidden wrote:

> A less intrusive (and hence less complete) solution:
> 
> - Create a new compilation-last-source-buffer variable.
> - At the end of next-error, set this new variable to the buffer just being
>       displayed.
> - at the beginning of next-error check compilation-last-source-buffer:
>   if it is equal to current-buffer, then don't consider this buffer as
>   a "compilation" buffer (i.e. ignore its next-error-function).
> 
> This way if a C-x ` lands us in a diff-mode buffer (because of a *grep* that
> points to a patch file), a subsequent C-x ` in the same buffer will not
> mistakenly step through the diffs of this buffer but will go to the next
> grep match.

I think my proposal to reorder the rules of next-error-find-buffer to
use next-error-last-buffer BEFORE (current-buffer) is essentially what
you are proposing.  If not, let me know.

Ted