|
| From: | Dmitry Gutov |
| Subject: | Re: conflicting uses of next-error-function |
| Date: | Wed, 29 Apr 2015 20:40:39 +0300 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 |
On 04/29/2015 07:58 PM, Helmut Eller wrote:
Maybe we could mark a buffer somehow that it's a reasonable candidate for next-error-last-buffer and have a command ala switch-buffer to select the current next-error-buffer from the list of candidates.
Yes, that sounds like the easiest approach. Then using next-error-function in xref at least won't make things worse.
The "mark a buffer somehow that it's a reasonable candidate" is an important step, because even plain buffers can have local next-error-function values, set by Flycheck or Flymake, for instance.
How will we do that?
| [Prev in Thread] | Current Thread | [Next in Thread] |