From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: nnchoke-request-update-mark
Date: Sat, 08 Sep 2001 01:31:53 -0400 [thread overview]
Message-ID: <m3ofom9rj4.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <Pine.LNX.4.33.0109070013170.17042-100000@lie.extundo.com> (Simon Josefsson's message of "Fri, 7 Sep 2001 00:19:24 +0200 (CEST)")
Simon Josefsson <jas@extundo.com> wrote:
> But, be sure to check that `nnchoke-request-update-mark' really does,
> chances are you don't want to use it.
I was going to have a per-group configurable list of prohibited marks;
these would be screened out with -request-update-mark. The particular
use I had in mind was protecting myself from accidentally marking
articles as expirable in certain groups; for this use, it wouldn't be
sufficient to just skip storing the marks.
If this were to be done, it ought to go in Gnus proper, not backends,
but I was going to do it as a proof-of-concept sort of thing, like
nnmaildir's always-marks and never-marks.
paul
prev parent reply other threads:[~2001-09-08 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 21:49 nnchoke-request-update-mark Paul Jarc
2001-09-06 12:57 ` nnchoke-request-update-mark Kai Großjohann
2001-09-06 22:19 ` nnchoke-request-update-mark Simon Josefsson
2001-09-08 5:31 ` Paul Jarc [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=m3ofom9rj4.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).