From: Norman Walsh <norm@berkshire.net>
Cc: ding@gnus.org
Subject: Re: B m creates duplicates?
Date: 19 May 1997 14:55:58 -0400 [thread overview]
Message-ID: <qa2073nvep.fsf@norm.berkshire.net> (raw)
In-Reply-To: Norman Walsh's message of 19 May 1997 11:16:06 -0400
Norman Walsh <norm@berkshire.net> writes:
> dsg@linus.mitre.org (David S. Goldberg) writes:
>
> > > Norman Walsh <norm@berkshire.net> writes:
> > >> I've just started using "B m" to move mail between groups (mostly
> > >> so I can have even greater refinement than I can practically create
> > >> with procmail) and I notice that articles moved this way are
> > >> flagged as duplicates.
> >
> > > Uhm... What do you mean by that they are "flagged as duplicates"?
> > > What does this flag look like?
> >
> > I bet he means they're flagged with a 'M' in the summary buffer of the
> > group they've been moved to if you read it in the same session you did
> > the move (did that sentence actually parse?). I've seen this too,
> > though I'm not really bothered by it. They don't show up as duplicate
> > if you read them in a subsequent session of gnus. I'm guessing they
> > should be removed from the message-id cache as part of the move.
>
> What he said ;-)
Ah, but one more point. I happen to be running 5.4.45 on another
machine and that version _does not_ exhibit the duplicate problem.
I was running 5.4.52 under NT when I saw the problem.
Cheers,
norm
--
Norman Walsh <nwalsh@arbortext.com> | The eternal mystery of the world
Senior Application Analyst | is its comprehensibility. -- A.
ArborText, Inc. (www.arbortext.com) | Einstien
413.549.3868 Voice/FAX |
next prev parent reply other threads:[~1997-05-19 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-17 16:27 Norman Walsh
1997-05-19 0:30 ` Lars Magne Ingebrigtsen
1997-05-19 12:51 ` David S. Goldberg
1997-05-19 15:16 ` Norman Walsh
1997-05-19 18:55 ` Norman Walsh [this message]
1997-05-20 20:20 ` 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=qa2073nvep.fsf@norm.berkshire.net \
--to=norm@berkshire.net \
--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).