From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: mail-sources backend specific?
Date: Tue, 06 May 2003 15:55:07 -0400 [thread overview]
Message-ID: <m3d6ivvoi6.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <84znm0ujee.fsf@lucy.is.informatik.uni-duisburg.de> (Kai =?iso-8859-1?q?Gro=DFjohann's?= message of "Tue, 06 May 2003 18:31:05 +0200")
kai.grossjohann@gmx.net (Kai Großjohann) wrote:
> prj@po.cwru.edu (Paul Jarc) writes:
>> nnmaildir does not use nnoo, and its server parameters are not
>> prefixed with "nnmaildir-". It does not use global variables to
>> represent its server parameters. So there is no problem here:
>
> Well, err, it sounds as if the mail-sources trick wouldn't work for
> nnmaildir in that case.
It's not such a big deal for that particular variable, since you can
safely deliver messages directly to nnmaildir groups.
> Oh! There is already a mechanism for local variables -- the
> buffers. So do people think it would work to set the variables local
> to the right buffers?
What buffer is nnchoke-request-scan called from? That's where
mail-sources will be used, I think.
> Complicated. I don't like it. But I think it's just the current
> design. Is there a chance for making it more sane?
I still think the situation could be greatly improved by moving the
work of nnmail-get-new-mail out of backends and into Gnus proper. It
would be a lot of work, but it could be done with minimal changes to
existing configurations while enabling all the flexibility we'd like.
paul
next prev parent reply other threads:[~2003-05-06 19:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 12:22 Using different backends Andreas Jaeger
2003-04-27 15:25 ` Kai Großjohann
2003-04-27 19:06 ` Andreas Jaeger
2003-05-02 13:03 ` Michael Teichgräber
2003-05-02 13:30 ` Kai Großjohann
2003-05-02 14:26 ` Michael Teichgräber
2003-05-02 14:47 ` Kai Großjohann
2003-05-02 15:15 ` Michael Teichgräber
2003-05-03 15:51 ` mail-sources backend specific? (was: Using different backends) Michael Teichgräber
2003-05-03 17:25 ` mail-sources backend specific? Kai Großjohann
2003-05-03 20:00 ` Michael Teichgräber
2003-05-03 20:57 ` Kai Großjohann
2003-05-04 2:40 ` Michael Teichgräber
2003-05-04 13:29 ` Kai Großjohann
2003-05-05 16:38 ` Paul Jarc
2003-05-06 16:31 ` Kai Großjohann
2003-05-06 19:55 ` Paul Jarc [this message]
2003-05-29 14:27 ` Kai Großjohann
2003-05-29 16:14 ` Paul Jarc
2003-10-18 12:53 ` Lars Magne Ingebrigtsen
2003-05-03 17:21 ` Using different backends Kai Großjohann
2003-05-03 19:00 ` Michael Teichgräber
2003-05-03 20:00 ` Kai Großjohann
2003-04-28 18:58 ` Paul Jarc
2003-04-29 5:45 ` Andreas Jaeger
2003-04-29 15:23 ` Paul Jarc
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=m3d6ivvoi6.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).