From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: tricky explicit interactive verbosity
Date: Tue, 14 Nov 2017 08:22:33 -0800 [thread overview]
Message-ID: <877eusu8xi.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86inef4cmf.fsf@zoho.com>
Emanuel Berg <moasen@zoho.com> writes:
> From `gnus-message':
>
> Guideline for numbers:
> 1 - error messages, 3 - non-serious error
> messages, 5 - messages for things that take
> a long time, 7 - not very important
> messages on stuff, 9 - messages
> inside loops.
>
> On the other hand `gnus-summary-current-score',
> being an interactive function even with
> a binding (`V S' in summary), it is a bit
> confusing that with `gnus-verbose' at 0, which
> you might not think of at the moment, nothing
> is outputted even when the user explicitely
> calls for the score output!
>
> Perhaps gnus-summary-current-score should
> always echo the score when used interactively?
> And only when used programmatically refer to the
> verbosity level?
It doesn't look like `gnus-summary-current-score' is used
programmatically at all, so I'm not sure why it would need to use
gnus-message in the first place. Other code can (and does) use whichever
of `gnus-summary-article-score' or `gnus-thread-total-score' is
necessary.
I'd be in favor of just using `message'.
Eric
next prev parent reply other threads:[~2017-11-14 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 17:42 Emanuel Berg
2017-11-14 16:22 ` Eric Abrahamsen [this message]
2017-11-14 20:16 ` Emanuel Berg
2017-11-14 21:53 ` Eric Abrahamsen
2017-11-20 22:23 ` Eric Abrahamsen
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=877eusu8xi.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).