From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: avoid clash between multiple mail backends
Date: 14 Apr 2000 20:48:44 +0200 [thread overview]
Message-ID: <vafsnwoh62b.fsf@lucy.cs.uni-dortmund.de> (raw)
As Easter is approaching, and hence Lars' Gnus hacking frenzy, I
thought I'd bring up the multiple mail backends issue.
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. Basically, nnml and nnfolder
try to read the same active file, and each one is mightily confused
about the entries from the other.
WIBNI something were done about this? What _could_ be done about
this?
kai
--
The birch trees fly way too low these days.
next reply other threads:[~2000-04-14 18:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-14 18:48 Kai Großjohann [this message]
2000-04-14 19:17 ` Karl Kleinpaste
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=vafsnwoh62b.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).