From: Michael Sperber <sperber@deinprogramm.de>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Patch submission: Allow group-local mail sources for nnmail
Date: Fri, 04 Jan 2008 08:24:19 +0100 [thread overview]
Message-ID: <y9l3atenjdo.fsf@deinprogramm.de> (raw)
In-Reply-To: <86r6gyvlj4.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 03 Jan 2008 11:58:23 -0600")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Thu, 03 Jan 2008 15:12:46 +0100 Michael Sperber <sperber@deinprogramm.de> wrote:
>
> MS> Thanks for the review - is this better?
>
> Looks great. 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?
--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
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--
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
next prev parent reply other threads:[~2008-01-04 7:24 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 [this message]
2008-01-04 11:59 ` Reiner Steib
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=y9l3atenjdo.fsf@deinprogramm.de \
--to=sperber@deinprogramm.de \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.com \
/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).