From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Michael Sperber <sperber@deinprogramm.de>
Cc: ding@gnus.org
Subject: Re: Patch submission: Allow group-local mail sources for nnmail
Date: Fri, 04 Jan 2008 12:59:04 +0100 [thread overview]
Message-ID: <v9hcht2453.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <y9l3atenjdo.fsf@deinprogramm.de> (Michael Sperber's message of "Fri, 04 Jan 2008 08:24:19 +0100")
On Fri, Jan 04 2008, Michael Sperber wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Could you add an example of a mail-source use to the manual, as
>> both the actual setting you'd use, and what it does?
>
> Like so?
Clearer than before.
> --snip--
> The @code{mail-sources} is global for all mail groups. You can specify
> an additional mail source for a particular group by including the
> @code{group} mail specifier in @code{mail-sources}, and setting a
> @code{mail-source} group parameter (@pxref{Group Parameters}) specifying
> a single mail source. When this is used, @code{mail-sources} is
> typically just @code{(group)}; the @code{mail-source} parameter for a
> group might look like this:
>
> @lisp
> (mail-source . (file :path "home/user/spools/foo.spool")
> (group)
> @end lisp
Missing ")" (in the first line?).
I don't understand the "(group)" here. I would have thought "(group)"
must appear in the `mail-sources' variable, but not in the group
parameter.
> This means that the group's (and only this group's) messages will be
> fetched from the spool file @code{home/user/spools/foo.spool}.
> --snip--
This should probably read @samp{/home/user/spools/foo.spool} (absolute
file name and @samp{}).
I think when using a `file' mail source in the group parameter, a
similar setup can already be achieved using a `directory' mail source
(though it doesn't allow fetching only a single source).
But you mentioned that you fetch from several IMAP folders to local
(nnml?) groups. i.e. you need to add a full `imap' mail source for
each group or do you use some function or macro for the setup?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-01-04 11:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 17:23 Michael Sperber
2008-01-02 19:29 ` Reiner Steib
2008-01-03 6:48 ` Michael Sperber
2008-01-03 12:42 ` Ted Zlatanov
2008-01-03 14:12 ` Michael Sperber
2008-01-03 17:58 ` Ted Zlatanov
2008-01-04 7:24 ` Michael Sperber
2008-01-04 11:59 ` Reiner Steib [this message]
2008-01-04 12:28 ` Michael Sperber
2008-01-16 7:20 ` Michael Sperber
2008-01-24 22:23 ` Reiner Steib
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=v9hcht2453.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=sperber@deinprogramm.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).