Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: automatically splitting conversations
Date: Sat, 10 Jun 2000 21:27:52 +0200	[thread overview]
Message-ID: <vafsnulibev.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Arnd Kohrs's message of "09 Jun 2000 13:04:12 +0200"

I have devised a patch for Gnus which does the following: whenever a
message is written to a group, Gnus memorizes the message id and the
group name.  There is a function which looks at the References header
of an incoming message and searches the memorized message ids for a
group name.  If a group name is found, it is returned.  If non is
found, nil is returned.

This does what you want, I think: you just `B m' the message into a
group, and all followups (and followups to the followups) go into that
group by default.

For the patch to work, you have to set nnmail-treat-duplicates to a
non-nil value.  And then you have to use the function
nnmail-split-fancy-with-parent in your split method.  I use
nnmail-split-fancy, as follows:

(setq nnmail-treat-duplicates 'delete) ;you might prefer `warn'
(setq nnmail-split-methods 'nnmail-split-fancy)
(setq nnmail-split-fancy '(| (: nnmail-split-fancy-with-parent)
                             ...other splits go here...))

I think the patch was integrated into Gnus on 2000-04-21, so it should
be in Gnus 5.8.6.

Hm.  I wonder if this is documented.  Hm.  No, apparently not.  This
is bad.  Please tell me how it goes when you try this.  I might need
your experience for writing the documentation.  Thanks!

kai
-- 
I like BOTH kinds of music.



  reply	other threads:[~2000-06-10 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-09 11:04 Arnd Kohrs
2000-06-10 19:27 ` Kai Großjohann [this message]
2000-06-11 20:22   ` Arnd Kohrs
2000-06-12 12:30     ` Arnd Kohrs

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=vafsnulibev.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --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).