Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: A recurring problem with multi-copies
Date: 13 Aug 2000 12:23:42 -0700	[thread overview]
Message-ID: <m2hf8pezi9.fsf@ognus-5.8.8-cvs.now.playing> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "13 Aug 2000 20:43:13 +0200"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
> 
> > I'd like some built in (or add on) way where gnus would tell me that I
> > already have copies of the dup messages in `t.awk' group, and asks if
> > I want to copy them anyway... or something similar.
> 
> I think that sounds too complex.

Just dealing with nnml for a moment, what would it really take?  The
nov file already contains the message-ids of those in the group.

Just guessing here, but could some kind of hook into `B c' `B m' call a
function that would scan the message-ids of the incoming messages, and
compare them to the existing nov info in target `nnml' group?

If that were done would it slow things down terribly?

Lets say a match occurs, immediately gnus spits out a message. 
`Some messages already present in TARGET group.. continue?
User hits `y' and gnus makes the move.  
User hits `n' and gnus only moves those messages whos ids *do not*
match the nov info.  Any matching message are left out.

This would be quite an enhancement for those of us who copy and move
stuff around extensively... and are senile and forgetful.




      reply	other threads:[~2000-08-13 19:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-11 13:38 Harry Putnam
2000-08-13 18:43 ` Lars Magne Ingebrigtsen
2000-08-13 19:23   ` Harry Putnam [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=m2hf8pezi9.fsf@ognus-5.8.8-cvs.now.playing \
    --to=reader@newsguy.com \
    /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).