From: Greg Troxel <gdt@lexort.com>
To: Teemu Likonen <tlikonen@iki.fi>
Cc: Dave Abrahams <dave@boostpro.com>, ding@gnus.org
Subject: Re: Lower all threads started by a particular tro... er, person?
Date: Sun, 07 Feb 2016 12:35:40 -0500 [thread overview]
Message-ID: <smutwlkfmoj.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <smu1t8oh1v4.fsf@linuxpal.mit.edu> (Greg Troxel's message of "Sun, 07 Feb 2016 12:22:23 -0500")
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
Sort of related, I find the docs hard to follow, and I think this might
be because of the score lowering function reads characters rather than
being a command prefix. I can see why it does this; it seems like they
are parameters, but it means the command docs don't explain the subcases:
gnus-summary-lower-score is an interactive autoloaded compiled Lisp
function in `gnus-score.el'.
(gnus-summary-lower-score &optional SCORE SYMP)
Make a score entry based on the current article.
The user will be prompted for header to score on, match type,
permanence, and the string to be used. The numerical prefix will
be used as SCORE. A symbolic prefix of `a' (the SYMP parameter)
says to use the `all.SCORE' file for the command instead of the
current score file.
[back]
Even reading the source, the behavior of followup is not entirely clear.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 180 bytes --]
next prev parent reply other threads:[~2016-02-07 17:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 7:39 Dave Abrahams
2016-01-08 14:05 ` Dave Marquardt
2016-01-09 7:36 ` Steinar Bang
2016-01-09 9:45 ` Adam Sjøgren
2016-01-09 10:58 ` Steinar Bang
2016-01-11 23:36 ` Dave Abrahams
2016-02-06 6:04 ` Lars Ingebrigtsen
2016-02-07 15:58 ` Dave Abrahams
2016-02-07 16:43 ` Teemu Likonen
2016-02-07 17:22 ` Greg Troxel
2016-02-07 17:35 ` Greg Troxel [this message]
2016-02-08 5:20 ` Lars Ingebrigtsen
2016-02-07 20:21 ` Dave Abrahams
2016-02-08 5:20 ` Lars Ingebrigtsen
2016-02-07 16:56 ` Greg Troxel
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=smutwlkfmoj.fsf@linuxpal.mit.edu \
--to=gdt@lexort.com \
--cc=dave@boostpro.com \
--cc=ding@gnus.org \
--cc=tlikonen@iki.fi \
/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).