From: Daniel Clemente <dcl441-bugs@yahoo.com>
To: ding@gnus.org
Subject: Disallow using agent with nnimap
Date: Mon, 09 Feb 2009 13:53:02 +0100 [thread overview]
Message-ID: <87iqnj22mp.fsf@CPU107.opentrends.net> (raw)
Hi,
we all know that gnus-agent creates lots of problems with nnimap backends. Not only wrong count numbers, but also you can apparently lose unread e-mails when you enter a group (and then you don't see them again even with C-u M-g).
This makes the innocent user angry. I would like that users are not required to remember that nnimap+agent=chaos, but that Gnus remembers this to the user in case it is needed (i.e. when enabling it).
Could we add some sort of warning or confirmation to avoid enabling nnimap+agent by mistake?
At least until it is fixed.
-- Daniel
next reply other threads:[~2009-02-09 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 12:53 Daniel Clemente [this message]
2009-02-10 23:40 ` Kevin Greiner
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=87iqnj22mp.fsf@CPU107.opentrends.net \
--to=dcl441-bugs@yahoo.com \
--cc=ding@gnus.org \
/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).