From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Confused about crosspost marking behavior.
Date: 03 Nov 1999 09:02:16 +0100 [thread overview]
Message-ID: <vaf4sf4dmuv.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Rob Browning's message of "02 Nov 1999 22:50:29 -0600"
Rob Browning <rlb@cs.utexas.edu> writes:
> [...] Now I wouldn't have been surprised if it had either been
> marked the same as I marked it in the other group, or if it had not
> been marked at all, but to be marked differently both places was
> unexpected.
Yes, that's a strange behavior of Gnus. If you were to change from
auto-expire to total-expire, the behavior would be more dwim-like:
both messages would have been marked as read, which would have made
them expirable.
I wonder whether one can do interesting tricks with the current
behavior...
There is a problem, though: what should happen if the article is
cross-posted to several groups, and some of them are auto-expirable
and some of them aren't?
> (Also, it might be nice to be able to choose whether or not a given
> command affects just the current article, or all instances of it...)
Yes, that would be nice. It's been discussed on this list before, but
AFAIK, nothing much came of it.
kai
--
This gubblick contains many nonsklarkish English flutzpahs,
but the overall pluggandisp can be glorked from context. -- David Moser
next prev parent reply other threads:[~1999-11-03 8:02 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 [this message]
1999-11-03 17:41 ` Rob Browning
1999-11-03 18:48 ` Dan Christensen
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=vaf4sf4dmuv.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).