From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Yong <leapfrog.cc@gmail.com>
Cc: ding@gnus.org
Subject: Re: group in the mail-sources could not get mails
Date: Tue, 20 Aug 2013 14:14:00 +0900 [thread overview]
Message-ID: <b4mfvu5t04n.fsf@jpl.org> (raw)
In-Reply-To: <87zjsei0if.fsf@gmail.com>
Yong wrote:
> I use maildrop to deliver my mails to maildir directories,
> and use nnml as mail backend in Gnus.
> Because maildrop had taken care of the mail splitting,
> I don't want Gnus to splitting mails again.
> So I set the mail-sources variable to "group" in .gnus.el:
> (setq mail-sources '((group)))
> then use "G p" in the *Group* buffer to set the parameter of the group
> where I want my mails to go:
> ((mail-source . (maildir :path "/path/to/maildir")))
> However, this group can't get the mails.
As far as I read the code in question[1], this feature will work
if and only if you use `gnus-group-get-new-news-this-group' (M-g)
for a group that has the `mail-source' group parameter. The code
requires the group name to get the group parameter, however there
is no opportunity to pass the group name to the code if you use
`gnus-group-get-new-news' (g).
So, we can call this a bug. I have no idea to fix it, though.
[1] nnmail-get-new-mail-1
> And when I use "G c" to see the group parameters, I got:
> Unknown entries:
> INS DEL Lisp expression:
> (mail-source maildir :path "/path/to/maildir")
This is not a real problem. It's only that `G c' doesn't know
such a parameter.
> BTW, if I just use
> (setq mail-sources '((maildir :path "/path/to/maildir")))
> then Gnus get the mails normally.
Exactly.
prev parent reply other threads:[~2013-08-20 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 7:48 Yong
2013-08-20 5:14 ` Katsumi Yamaoka [this message]
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=b4mfvu5t04n.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=leapfrog.cc@gmail.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).