From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: avoid clash between multiple mail backends
Date: 14 Apr 2000 15:17:05 -0400 [thread overview]
Message-ID: <vxkg0sofq6m.fsf@mesquite.charcoal.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "14 Apr 2000 20:48:44 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Right now, if you (add-to-list 'gnus-secondary-select-methods '(nnml
> "")) and then (add-to-list 'gnus-secondary-select-methods '(nnfolder
> "")), nasty things are wont to happen...
> WIBNI something were done about this? What _could_ be done about this?
1. Do away with the idea of a single mail active file, and instead
instantiate active.nnFOO per-method active files.
2. Perform an implicit (setq nnFOO-get-new-mail nil) for the 2nd thru
Nth backends encountered.
For the latter, noting that there are some folks who set their primary
method to a mail backend, it won't be sufficient merely to work with
the 2nd through Nth elements of gnus-secondary-select-methods. If
gnus-select-method is a mail backend, then _all_ entries of
gnus-secondary-select-methods will have to have -get-new-mail set to
nil.
next prev parent reply other threads:[~2000-04-14 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-14 18:48 Kai Großjohann
2000-04-14 19:17 ` Karl Kleinpaste [this message]
2000-04-14 21:03 ` Kai Großjohann
2000-04-14 21:16 ` David S. Goldberg
2000-04-14 22:18 ` Kai Großjohann
2000-04-15 14:47 ` Karl Kleinpaste
2000-04-14 19:28 ` David S. Goldberg
2000-04-14 21:12 ` Kai Großjohann
2000-04-19 23:57 ` Lars Magne Ingebrigtsen
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=vxkg0sofq6m.fsf@mesquite.charcoal.com \
--to=karl@charcoal.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).