From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: How about one `gnus-summary-mark-as-ancient'?
Date: 06 Nov 1999 04:22:42 +0100 [thread overview]
Message-ID: <m3bt982tj1.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87zoxxjtf0.fsf@cs.tu-berlin.de>
Rui Zhu <sprache@iname.com> writes:
> When I reopened the old articles in a scored group accidentally or
> for test purpose, I'd like to mark it old (ancient) to prevent it
> being adaptive scored (I think few people will like to score on
> `gnus-ancient-mark', might be wrong?). Maybe I'm too paranoid, think
> if I've set `gnus-decay-scores' to `t'. Does some others think such a
> new command be handy so it can be merged into pgnus later?
Hm. I'm a bit leery of adding such a command to Gnus. I think it
might lead people to believe that they can persistantly mark articles
as ancient, when they really can't. That is, once they exit the
group, those marks will be gone again.
But I don't know. Whadday'allthink?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-11-06 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-05 23:10 Rui Zhu
1999-11-06 3:22 ` Lars Magne Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3bt982tj1.fsf@quimbies.gnus.org \
--to=larsi@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).