[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: improve "next locus from <buffer>" messages
From: |
Eli Zaretskii |
Subject: |
Re: improve "next locus from <buffer>" messages |
Date: |
Wed, 03 Apr 2019 21:20:07 +0300 |
> From: Stephen Leake <address@hidden>
> Date: Wed, 03 Apr 2019 09:50:20 -0800
>
> 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? If indeed some people are annoyed by these simple
messages, maybe a defcustom is in order, but changing the default
behavior unconditionally due to such reasons sounds gross to me.
Thanks.
- improve "next locus from <buffer>" messages, Stephen Leake, 2019/04/03
- Re: improve "next locus from <buffer>" messages,
Eli Zaretskii <=
- 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