Gnus development mailing list
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Subject: Re: More on the new nnimap
Date: Mon, 04 Oct 2010 17:14:44 -0400	[thread overview]
Message-ID: <m339slacdf.fsf@jhcloos.com> (raw)
In-Reply-To: <m3k4lxwxh4.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 04 Oct 2010 21:48:23 +0200")

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

LMI> James Cloos <cloos@jhcloos.com> writes:
LMI> What is your gnus-subscribe-newsgroup-method exactly? 

LMI> Right.  That should work.  Does `F' subscribe you to new nnimap groups,
LMI> or do you never see new nnimap groups?

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.

LMI> The ChangeLog message for this is:

LMI> 	(nnimap-open-shell-stream): Bind `process-connection-type' to nil, so
LMI> 	that CRLF doesn't get translated to \n.

LMI> So binding it to nil fixes a real bug.  Is there no way to get rid of
LMI> stderr without using a pty?        

The equic of stty raw on the pty also will fix that.

>> Creating the group, though, is to allow gnus access.

LMI> The create group command is really meant to create the group on the
LMI> backend.

Seems odd.

It never did that when I used nnmh, nor have I seen it with nnmaildir.

I obviously cannot do that for nntp.

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.

LMI> You can subscribe groups in Gnus, but if this has worked
LMI> before, it was probably an accident.  All the other backends create
LMI> groups in response to that command.

NIME.

LMI> So you'll have to adjust your code to have Gnus subscribe the group
LMI> instead of calling out `*-request-create-group' to the backend.



LMI> Why is `F' slow?  Which backends take long to respond?

Imap.  LIST only gets about 20 groups/second.  A direct sql query
reports the whole list of groups in 7+ ms.

Checking for \noinferiors and \hasnochildren is probably what slows it
down.

LMI> You use IMAP as the interface to a SQL-based mail storage?

When I gave up on nnmh (due to many of the bugs you recently fixed, but
also the cost of accessing so many inodes) dbmail-2.2 was the best option
available.  I had to write a patch to use dense, per-group UIDs instead
of sparse, per-server UIDs, but it was still better than the alternatives.

And it mostly still is.

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.

I just tried running LIST outside of gnus; the new groups are included.
One example is:

* LIST (\noinferiors \hasnochildren) "/" "gimp-announce@lists.xcf.berkeley.edu"

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6




  reply	other threads:[~2010-10-04 21:14 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 [this message]
2010-10-05 16:39         ` Lars Magne Ingebrigtsen
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=m339slacdf.fsf@jhcloos.com \
    --to=cloos@jhcloos.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).