From: gdt@work.lexort.com
Cc: ding@gnus.org
Subject: Re: 'g' not checking nnimap groups
Date: Tue, 04 Apr 2006 10:54:52 -0400 [thread overview]
Message-ID: <smuek0dmlvn.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <87y7ylbgb4.fsf@latte.josefsson.org> (Simon Josefsson's message of "Tue, 04 Apr 2006 15:50:39 +0200")
Simon Josefsson <jas@extundo.com> writes:
> Actually, the bug is how (nnimap "foo") ever got into your setup.
I agree that's a bug. I think I did U and then subscribed to a group,
before I realized the preferred way was to use server mode and browse.
> The server (nnimap "foo") isn't the same as (nnimap "foo" (nnimap-port
> ...) ...), and Gnus will treat them as different servers.
> Consequently, (nnimap "foo") is treated as an ephemeral server, and
> checked using the slow mechanism (I forgot the reason as to why, but
> it is probably because it is simpler to optimize the primary/secondary
> case).
But, gnus used the same imap server connection. The "foo" in the
wrong group spec isn't the same as the IMAP server, so it must have
used the nnimap select method in gnus-secondary-select-methods to find
it.
On my list of things to look into if I find spare time:
add path from UNSEEN count from STATUS to count of new articles in
summmary
investigate nnimap/agent cache coherency, ensuring articles
deleted/moved by other clients are removed from the agent.
--
Greg Troxel <gdt@work.lexort.com>
next prev parent reply other threads:[~2006-04-04 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 4:04 Problems with attachments in S/MIME encrypted messages from Outlook Dave Goldberg
2006-03-22 9:53 ` Simon Josefsson
2006-03-22 12:13 ` Dave Goldberg
2006-03-23 15:06 ` 'g' not checking nnimap groups gdt
2006-03-25 12:54 ` Simon Josefsson
2006-04-04 0:25 ` gdt
2006-04-04 12:36 ` Simon Josefsson
2006-04-04 13:46 ` gdt
2006-04-04 13:50 ` Simon Josefsson
2006-04-04 14:54 ` gdt [this message]
2006-04-04 16:37 ` Simon Josefsson
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=smuek0dmlvn.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.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).