all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: emacs-devel@gnu.org
Subject: Re: improve "next locus from <buffer>" messages
Date: Wed, 03 Apr 2019 21:20:07 +0300	[thread overview]
Message-ID: <83y34rc5ns.fsf@gnu.org> (raw)
In-Reply-To: <86sguzc71f.fsf@stephe-leake.org> (message from Stephen Leake on Wed, 03 Apr 2019 09:50:20 -0800)

> From: Stephen Leake <stephen_leake@stephe-leake.org>
> 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.



  reply	other threads:[~2019-04-03 18:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 17:50 improve "next locus from <buffer>" messages Stephen Leake
2019-04-03 18:20 ` Eli Zaretskii [this message]
2019-04-03 20:53   ` Stephen Leake
2019-04-03 21:22     ` Stephen Leake
2019-04-04  9:26       ` Felician Nemeth
2019-04-04 13:41         ` Stephen Leake
2019-04-04 14:09           ` Dmitry Gutov
2019-04-04 12:54     ` Eli Zaretskii
2019-04-04 13:55       ` Stephen Leake
2019-04-07 16:55         ` Stephen Leake
2019-04-08 19:21           ` Juri Linkov
2019-04-08 22:16             ` [SPAM UNSURE] " Stephen Leake
2019-04-13 20:56               ` Juri Linkov
2019-04-14 16:25                 ` [SPAM UNSURE] " Stephen Leake

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83y34rc5ns.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@stephe-leake.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.