From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37910 Path: main.gmane.org!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.gnus.general Subject: Re: Prevent B c/B m from createing dups in target group Date: 17 Aug 2001 12:25:20 -0700 Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035173579 18030 80.91.224.250 (21 Oct 2002 04:12:59 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 04:12:59 +0000 (UTC) Return-Path: Return-Path: Original-Received: (qmail 5840 invoked from network); 17 Aug 2001 19:25:24 -0000 Original-Received: from mail.networkone.net (209.144.112.246) by gnus.org with SMTP; 17 Aug 2001 19:25:24 -0000 Original-Received: (qmail 21582 invoked from network); 17 Aug 2001 19:25:22 -0000 Original-Received: from unknown (HELO reader.local.lan) (209.144.117.151) by mail.networkone.net with SMTP; 17 Aug 2001 19:25:22 -0000 Original-Received: (from reader@localhost) by reader.local.lan (8.11.2/8.11.0) id f7HJPKB18465; Fri, 17 Aug 2001 12:25:20 -0700 X-Authentication-Warning: reader.local.lan: reader set sender to reader@newsguy.com using -f Original-To: ding@gnus.org In-Reply-To: (Lars Magne Ingebrigtsen's message of "Fri, 17 Aug 2001 20:52:37 +0200") User-Agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.0.104 Original-Lines: 43 Xref: main.gmane.org gmane.emacs.gnus.general:37910 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:37910 Lars Magne Ingebrigtsen writes: > Harry Putnam writes: > > > With that warning mechanism in place, and provision to copy/move only > > the unique messages on command, a user could simply throw a batch of > > messages at a directory and only the unique stuff would stick... > > Yeah. But there is no predefined functionality in Gnus for doing > this.. My OP was asking for an outline of how to go about starting to create that functionality in gnus. Once finished it could hopefully be submitted for consideration as an inclusion. I'm pretty sure once this kind of functionality became known it would be seen as a nice addition. > 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... Possibly it is a non-problem but I see at least a few problems with that approach: 1) In the event I have edited the first copy in some way. Then later looking back at old threads I see that same message not realizing I've already copied and edited it to a save group. I copy it again but being in a hurry neglect to edit it. Which one will show up when duplicate suppression on entry is engaged? 2) I run up on an old thread in a Newsgroup. Maybe a discussion of `sender' and RFC provisions and decide I'd like to keep the whole thing... all 235 : ) messages. I've already piece meal saved 70, not necessaryily in order. I just throw the whole batch into a saved group, now I have at least 70 dups. Do I want that overhead? When I might possible be able to write something for gnus that would allow me to do that and only actually move the unique ones on my request. 3) Suppression seems very much like taking pain pills to mask an injury while continuing to grind your body to dust...