From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [SPAM UNSURE] Re: [SPAM UNSURE] Re: improve "next locus from <buffer>" messages
Date: Sun, 14 Apr 2019 08:25:17 -0800 [thread overview]
Message-ID: <86bm18wo42.fsf@stephe-leake.org> (raw)
In-Reply-To: <87muktbp4k.fsf@mail.linkov.net> (Juri Linkov's message of "Sat, 13 Apr 2019 23:56:43 +0300")
Juri Linkov <juri@linkov.net> writes:
>>>> +---
>>>> +** next-error-suppress-locus-message controls when `next-error'
>>>> + outputs a message about the error locus.
>>>
>>> Is this feature really expected to be used often to deserve the new
>>> defcustom or a simple defvar would be enough?
>>
>> If it's a defcustom, it is easier for people to find, if they are
>> bothered by the verbosity.
>>
>>> In any case I recommend to rename it to next-error-verbosity.
>>
>> ok.
>
> Sorry, I realized only after your commit that a better name would be
> next-error-verbose.
Makes sense
> Also this makes clear that the meaning of its value should be reversed -
> to show verbose messages when the value is non-nil.
Yes, I realized that when I went to set it.
> But I have no opinion about its default value, if you want you can
> change it from nil to t.
On the principle of least bother to others, I'll make the default be the
verbose setting.
Thanks for your help.
--
-- Stephe
prev parent reply other threads:[~2019-04-14 16:25 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
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 ` Stephen Leake [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86bm18wo42.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=emacs-devel@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).