From: Chris Tessone <tessone@imsa.edu>
Cc: ding@gnus.org
Subject: Re: M-x nnmail-split-history RET
Date: 14 Oct 1998 18:52:33 -500 [thread overview]
Message-ID: <x3ghfx68zwe.fsf@java.imsa.edu> (raw)
In-Reply-To: Kai Grossjohann's message of "14 Oct 1998 23:21:20 +0200"
>>>>> "Kai" == Kai Grossjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
Kai> Sometimes, I get a new mail and type g and then look at the
Kai> split history, and it's got >10 entries. Can't imagine that
Kai> I got that many mails. Maybe if the mail I got is a
Kai> duplicate (because I got it twice or because it's from me and
Kai> I've already got a Gcc'd copy), Gnus just silently deletes it
Kai> and it doesn't show up in the split history at all?
AFAIK, Gnus doesn't delete duplicates. That would be slightly
frightening.
Chris
--
Chris Tessone tessone@fnal.gov tessone@imsa.edu
PH/sendmail SNPC System Administration Perl/Shell
All you need is Perl, love. Perl is all you need.
http://www.imsa.edu/~tessone/
next prev parent reply other threads:[~1998-10-14 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-14 21:21 Kai Grossjohann
1998-10-14 23:52 ` Chris Tessone [this message]
1998-10-15 0:15 ` Francisco Solsona
1998-10-15 10:11 ` Kai Grossjohann
1998-10-17 20:59 ` 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=x3ghfx68zwe.fsf@java.imsa.edu \
--to=tessone@imsa.edu \
--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).