From: Dan Christensen <jdc@jhu.edu>
Cc: ding@gnus.org
Subject: Re: Confused about crosspost marking behavior.
Date: Wed, 03 Nov 1999 13:48:00 -0500 [thread overview]
Message-ID: <87aeovwgwv.fsf@chow.mat.jhu.edu> (raw)
In-Reply-To: Rob Browning's message of "03 Nov 1999 11:41:09 -0600"
Your ideas sound good to me. One minor suggestion:
> 6) Add a variable nnmail-crosspost-mark-query that, if true, asks
> the user what to do when gnus is about to mark a crossposted
> article (or articles):
The could be nnmail-crosspost-mark, which could have values t, nil or
'query, meaning to always do it, never do it, or query the user.
Dan
--
Dan Christensen
jdc@math.jhu.edu
next prev parent reply other threads:[~1999-11-03 18:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-03 4:50 Rob Browning
1999-11-03 8:02 ` Kai Großjohann
1999-11-03 17:41 ` Rob Browning
1999-11-03 18:48 ` Dan Christensen [this message]
1999-11-03 20:17 ` Sudish Joseph
1999-11-09 0:27 ` Justin Sheehy
1999-11-09 5:34 ` Rob Browning
1999-11-09 6:13 ` Rob Browning
1999-11-09 14:35 ` David S. Goldberg
1999-11-09 16:05 ` Rob Browning
1999-11-09 8:22 ` Hrvoje Niksic
1999-11-09 13:56 ` Yair Friedman (Jerusalem)
1999-11-03 19:03 ` Rob Browning
1999-11-07 1:10 ` Lars Magne Ingebrigtsen
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=87aeovwgwv.fsf@chow.mat.jhu.edu \
--to=jdc@jhu.edu \
--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).