[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: next-error use cases
From: |
Stephen Leake |
Subject: |
Re: next-error use cases |
Date: |
Thu, 12 Apr 2018 10:25:09 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (windows-nt) |
Dmitry Gutov <address@hidden> writes:
> On 4/11/18 6:26 AM, Stephen Leake wrote:
>
>>> But how can you reset it when the location list is in the same buffer
>>> like in case of flyspell where locations of misspelled words are
>>> in the same buffer where next-error navigates, or flymake where
>>> locations of errors/warnings are in the same buffer?
>>
>> Position point on an error message, hit enter.
>
> The error message is usually visible only in the minibuffer, and only
> when point is over the error.
Ok. So add a keybinding that says "there is an error under point; use
the list it is part of as the current error list".
Presumably you already have "goto error under point"; that should also
set the current list.
(How do you notice there is an error there, so you know to position point?
a marker in the margin?)
I gather there might be more than one such list in a single buffer, so
compilation-last-buffer is insufficient.
You might be able to extend that; if it is a cons, the car is the
buffer, the car the root list element, or the list type tag, or
something.
--
-- Stephe
- Re: next-error use cases, (continued)
- Re: next-error use cases, Dmitry Gutov, 2018/04/08
- Re: next-error use cases, Eli Zaretskii, 2018/04/09
- Re: next-error use cases, Charles A. Roelli, 2018/04/09
- Re: next-error use cases, Juri Linkov, 2018/04/09
- Re: next-error use cases, Stephen Leake, 2018/04/10
- Re: next-error use cases, Juri Linkov, 2018/04/10
- Re: next-error use cases, Stephen Leake, 2018/04/10
- Re: next-error use cases, Dmitry Gutov, 2018/04/11
- Re: next-error use cases, Juri Linkov, 2018/04/11
- Re: next-error use cases, Stephen Leake, 2018/04/12
- Re: next-error use cases,
Stephen Leake <=
- Re: next-error use cases, Dmitry Gutov, 2018/04/12
- Re: next-error use cases, Stephen Leake, 2018/04/13
- Re: next-error use cases, Dmitry Gutov, 2018/04/13
- Re: next-error use cases, Dmitry Gutov, 2018/04/10
Re: next-error use cases, Juri Linkov, 2018/04/12