Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: nnimap and split with parent
Date: Tue, 04 Jun 2002 12:49:40 +0200	[thread overview]
Message-ID: <vafit4ze2t7.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <xtzd6v7z74n.fsf@dolormin.informatik.uni-bremen.de>

Andreas Büsching <crunchy@tzi.de> writes:

> As everybody can see I'm using Oort Gnus und as one mail backend I'm
> using nnimap. With the current CVS version of Oort Gnus nnimap works
> very fine and fast. Just one more feature I would like to have: For some
> other mail backend[1] there is a function called
> nnmail-split-fancy-with-parent (or somehting like that). Is can be used
> to move mails into the same folder as there parents. is there any way to
> have this feature with nnimap?

It would be fairly easy to change nnimap splitting such that it looks
at ~/.nnmail-cache.  But you have to change more code in nnmail.el so
that it works well with nnimap.

Currently, the whole thing is rather limited, I'm afraid: it works
only for one backend.  It stores group names without the server name
in .nnmail-cache and if the `primary mail backend' changes all that
data is bogus.

Wasn't there somebody working on changing this?  I forget.  But I
think you will find something in the archives for the Gnus mailing
list.

kai
-- 
Silence is foo!


  reply	other threads:[~2002-06-04 10:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 10:10 Andreas Büsching
2002-06-04 10:49 ` Kai Großjohann [this message]
2002-06-04 13:54   ` Andreas Büsching
     [not found]     ` <vafznybf619.fsf@lucy.cs.uni-dortmund.de>
     [not found]       ` <xtzhekjxan4.fsf@dolormin.informatik.uni-bremen.de>
     [not found]         ` <vafu1oi138t.fsf@lucy.cs.uni-dortmund.de>
     [not found]           ` <xtzvg8y3pl7.fsf@dolormin.informatik.uni-bremen.de>
     [not found]             ` <vafhekhx3n0.fsf@lucy.cs.uni-dortmund.de>
     [not found]               ` <xtzhekg51n2.fsf@dolormin.informatik.uni-bremen.de>
2002-06-06 12:08                 ` Kai Großjohann
2002-06-06 14:08                   ` Andreas Büsching
     [not found]                     ` <vafd6v4e3lt.fsf@lucy.cs.uni-dortmund.de>
     [not found]                       ` <iluit4wnsdl.fsf@latte.josefsson.org>
     [not found]                         ` <vafvg8vzbnz.fsf@lucy.cs.uni-dortmund.de>
     [not found]                           ` <xtzadq7mg8c.fsf@dolormin.informatik.uni-bremen.de>
     [not found]                             ` <vafadq7rl6o.fsf@lucy.cs.uni-dortmund.de>
     [not found]                               ` <xtzptyzlkkd.fsf@dolormin.informatik.uni-bremen.de>
2002-06-11 15:05                                 ` Kai Großjohann
     [not found] ` <m3adqb2i7f.fsf@ID-87814.user.dfncis.de>
2002-06-04 16:02   ` x-face with greys Andreas Büsching
     [not found]     ` <m34rgij8k3.fsf@ID-87814.user.dfncis.de>
     [not found]       ` <ufseiojda72428@news.supernews.com>
2002-06-06  5:29         ` J.B. Moreno

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