From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: More on the new nnimap
Date: Tue, 05 Oct 2010 18:39:30 +0200 [thread overview]
Message-ID: <m3y6ac7fwd.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m339slacdf.fsf@jhcloos.com>
James Cloos <cloos@jhcloos.com> writes:
> Not now (still on commit 43de9c6fe344). It only (claimed to) subscribe(d)
> one group which wasn't actually new.
>
> The 29 new groups were ignored.
nnimap-request-newgroups returned nil, so it was ignored. This might
work now...
> The equic of stty raw on the pty also will fix that.
Do you know how to do that?
> It never did that when I used nnmh, nor have I seen it with nnmaildir.
Reading the code, it looks like it does:
(deffoo nnmh-request-create-group (group &optional server args)
[...]
(nnmh-possibly-create-directory group)
> And there is nothing in the doc string to suggest that Gm would make any
> changes on any server, just that it tells gnus to create a group to read
> ADDRESS.
I've now updated the doc.
> Imap. LIST only gets about 20 groups/second. A direct sql query
> reports the whole list of groups in 7+ ms.
[...]
> LMI> Anyway, for nnimap `F' just issues a LIST command. Does a LIST in your
> LMI> setup take minutes?
>
> About 13. And gnus ignored the new groups.
So you have (* 20 60 13) => 15600 IMAP groups?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-10-05 16:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 18:23 James Cloos
2010-10-04 16:36 ` Lars Magne Ingebrigtsen
2010-10-04 18:02 ` James Cloos
2010-10-04 19:48 ` Lars Magne Ingebrigtsen
2010-10-04 21:14 ` James Cloos
2010-10-05 16:39 ` Lars Magne Ingebrigtsen [this message]
2010-10-05 22:01 ` Dan Christensen
2010-10-07 19:11 ` Lars Magne Ingebrigtsen
2010-10-08 15:47 ` James Cloos
2010-10-06 9:05 ` James Cloos
2010-10-07 19:22 ` Lars Magne Ingebrigtsen
2010-10-08 16:00 ` James Cloos
2010-10-09 16:06 ` 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=m3y6ac7fwd.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).