[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: improve "next locus from <buffer>" messages
From: |
Stephen Leake |
Subject: |
Re: improve "next locus from <buffer>" messages |
Date: |
Wed, 03 Apr 2019 13:22:15 -0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (windows-nt) |
Stephen Leake <address@hidden> writes:
> Eli Zaretskii <address@hidden> writes:
>
>>> Currently, next-error always outputs a message "next locus from
>>> <buffer>". In the vast majority of cases, <buffer> does not change from
>>> one message to the next, so this message is just annoying.
>>>
>>> The attached patch changes it so the message is only output when the
>>> locus changes.
>>>
>>> It also gets rid of the "first/current/previous" options; what matters
>>> is where the _next_ error will come from.
>>>
>>> Comments?
>>
>> Comment: why change long-time default behavior based on personal
>> preferences?
>
> These messages are not in emacs-26, so I don't think they count as
> "long-time".
If you are refering to the "first/current/previous", they were not
always accurate; often the first error from a locus prints "next error
from ...", because next-error is invoked without reset.
--
-- Stephe
- improve "next locus from <buffer>" messages, Stephen Leake, 2019/04/03
- Re: improve "next locus from <buffer>" messages, Eli Zaretskii, 2019/04/04
- Re: improve "next locus from <buffer>" messages, Stephen Leake, 2019/04/04
- Re: improve "next locus from <buffer>" messages, Stephen Leake, 2019/04/07
- Re: improve "next locus from <buffer>" messages, Juri Linkov, 2019/04/08
- Re: [SPAM UNSURE] Re: improve "next locus from <buffer>" messages, Stephen Leake, 2019/04/08
- Re: [SPAM UNSURE] Re: improve "next locus from <buffer>" messages, Juri Linkov, 2019/04/13
- Re: [SPAM UNSURE] Re: [SPAM UNSURE] Re: improve "next locus from <buffer>" messages, Stephen Leake, 2019/04/14