From: Bastien <bzg@altern.org>
To: ding@gnus.org
Subject: Re: released mairix backend nnmairix.el
Date: Sun, 07 Oct 2007 00:17:48 +0100 [thread overview]
Message-ID: <878x6fkf37.fsf@bzg.ath.cx> (raw)
In-Reply-To: <kzhcl4vt7f.fsf@musil.physik3.gwdg.de> (David's message of "Sat, 06 Oct 2007 23:17:24 +0200")
David <de_bb@arcor.de> writes:
> This means, the 'base' path in .mairixrc and the base path of your
> mail folders have to be the same.
Yes, this is the bit of information that needs to be clearer in the
documentation IMO.
The problem is that people that have been using mairix + gnus before
nnmairix.el might be used to have a specific backend/folder for mairix
results. For example I had a nnmaildir backend + linked to the folder I
had set up in ~/.mairixrc as my "mfolder"...
--
Bastien
next prev parent reply other threads:[~2007-10-06 23:17 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 [this message]
2007-10-07 11:12 ` Georg C. F. Greve
2007-10-07 15:53 ` David
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=878x6fkf37.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).