From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Prevent B c/B m from createing dups in target group
Date: Fri, 17 Aug 2001 21:08:02 +0200 [thread overview]
Message-ID: <vafy9oitsh9.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3r8uav7re.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 17 Aug 2001 20:52:37 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Yeah. But there is no predefined functionality in Gnus for doing
> this, and I think it sounds like something of a non-problem. :-)
> When you suppress duplicate messages on group entry, you usually just
> see one copy in any case, no matter how many are actually there...
Well, but Harry is copying messages, and copying the same message
several times doesn't make sense.
The reason Harry is copying several times is because he sees an
interesting thread, then possibly edits the messages in that thread,
then he copies the messages into an archive group. There's no way for
him to (easily) see which messages were copied already.
Hm. Maybe a different approach is possible altogether?
If it wasn't for the editing, saving the messages in the cache (via
`*') would be enough. Hm.
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2001-08-17 19:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 15:40 Harry Putnam
2001-08-17 17:28 ` Kai Großjohann
2001-08-17 18:20 ` Harry Putnam
2001-08-17 18:52 ` Lars Magne Ingebrigtsen
2001-08-17 18:58 ` Paul Jarc
2001-08-17 19:01 ` Lars Magne Ingebrigtsen
2001-08-17 19:08 ` Kai Großjohann [this message]
2001-08-17 19:21 ` Lars Magne Ingebrigtsen
2001-08-17 19:45 ` Harry Putnam
2001-08-17 19:25 ` Harry Putnam
2001-08-17 19:40 ` Lars Magne Ingebrigtsen
2001-08-17 19:47 ` Paul Jarc
2001-08-17 20:24 ` Lars Magne Ingebrigtsen
2001-08-17 20:35 ` Harry Putnam
2001-08-17 19:09 ` Kai Großjohann
2001-08-17 19:55 ` Harry Putnam
2001-08-17 20:50 ` Kai Großjohann
2001-08-19 15:57 ` Nuutti Kotivuori
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=vafy9oitsh9.fsf@INBOX.auto.gnus.tok.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).