[Top][All Lists]

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

Re: next-error use cases

From: Eli Zaretskii
Subject: Re: next-error use cases
Date: Fri, 13 Apr 2018 10:45:34 +0300

> From: Juri Linkov <address@hidden>
> Date: Thu, 12 Apr 2018 23:27:16 +0300
> Since we removed the rule of visibility of next-error-function buffers
> as a criteria for deciding what navigation to use for next-error,
> so e.g. next-error in *Occur* or *Diff* that is the current buffer
> and a single visible buffer on the frame will still use the last next-error
> buffer that might be e.g. *compilation* or *grep* buffer buried long ago,
> now we need to support the same way to switch next-error navigation as
> already is possible in *compilation* and *grep* by typing RET or ‘C-c C-c’
> that sets next-error-last-buffer in next-error-internal among other things.

Sorry, I don't understand what kind of solution are you proposing in
user terms.  Can you please describe what the user should do under the
proposed solution in various cases, such as if they need to invoke
navigation in the current Occur buffer or in a Compilation/Grep
buffer, either shown or not shown?

reply via email to

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