Gnus development mailing list
 help / color / mirror / Atom feed
From: David <de_bb@arcor.de>
To: ding@gnus.org
Cc: greve@fsfeurope.org
Subject: Re: released mairix backend nnmairix.el
Date: Sun, 07 Oct 2007 17:53:19 +0200	[thread overview]
Message-ID: <kz641ix6og.fsf@musil.physik3.gwdg.de> (raw)
In-Reply-To: <m3r6k7b2lb.fsf@cerebro.fsfeurope.org>

"Georg C. F. Greve" <greve@fsfeurope.org> writes:
> I think nnmairix should use 'nnml-directory' instead, which is where the
> path for the mail folders are configured in Gnus, or the appropriate
> variable for other backends.

That's a good idea. This could be done for all backends except nnimap,
where the base path in .mairixrc would still have to point to the
Maildir directory the IMAP server uses.

> As an added benefit, nnmairix should then also work in situations with
> "mixed" backends, because they are not illegal, some people use them for
> reasons that may not be entirely obvious, and nnmairix should not choke
> on this, imho.

Well, the nnmairix commands in group mode should already work with mixed
backends, but you have to adapt all paths in your .mairixrc
accordingly. Set your 'base' variable to '~/Mail' and adapt all
following lines relative to this base path. If your archive mbox files
are not under ~/Mail but e.g. under ~/mailarchive, you have to use
something like

mbox=../mailarchive/2005/*:../mailarchive/2006/*

However, the commands in summary mode will not work in these archive
groups, since I originally had the idea that every nnmairix server would
be "responsible" for exactly one backend. I overlooked that people may
use several backends for local mail but which are indexed by one mairix
installation.

Your idea also has the benefit that people which are uncomfortable with
nnmairix creating those zz_mairix-groups alongside their normal mail
folders could still create e.g. a nnmaildir server only for the mairix
search folders.

Regards,
David




  reply	other threads:[~2007-10-07 15:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 13:52 Getting rid of the zombies in dynamically created groups Georg C. F. Greve
2007-09-26 18:38 ` Reiner Steib
2007-09-26 22:38   ` Georg C. F. Greve
2007-09-27  6:12     ` Reiner Steib
2007-09-27 21:35       ` Georg C. F. Greve
2007-10-04  8:04 ` released mairix backend nnmairix.el (was: Getting rid of the zombies in dynamically created groups) David
2007-10-04 16:29   ` released mairix backend nnmairix.el Reiner Steib
2007-10-05  9:15     ` David
2007-10-05 16:41       ` Reiner Steib
2007-10-06 14:24       ` Georg C. F. Greve
2007-10-06 18:59         ` Bastien
2007-10-06 21:20           ` David
2007-10-06 23:19             ` Bastien
2007-10-07 16:09               ` David
2007-10-08  9:33                 ` Bastien
2007-10-06 21:17         ` David
2007-10-06 23:17           ` Bastien
2007-10-07 11:12           ` Georg C. F. Greve
2007-10-07 15:53             ` David [this message]
2007-10-08  9:33               ` Bastien
2007-10-04 16:48   ` released mairix backend nnmairix.el (was: Getting rid of the zombies in dynamically created groups) Bastien
2007-10-04 17:18     ` released mairix backend nnmairix.el Bastien
2007-10-05  9:46       ` David
2007-10-05 12:00         ` Bastien
2007-10-04 23:54   ` Bastien

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=kz641ix6og.fsf@musil.physik3.gwdg.de \
    --to=de_bb@arcor.de \
    --cc=ding@gnus.org \
    --cc=greve@fsfeurope.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).