Gnus development mailing list
 help / color / mirror / Atom feed
From: "Steven E. Harris" <seh@panix.com>
Cc: "Simon Josefsson" <jas@extundo.com>
Subject: Re: nnimap problem solved by removing .agentview and .overview
Date: Mon, 16 Aug 2004 12:54:06 -0700	[thread overview]
Message-ID: <jk4wtzyoo4h.fsf@W003275.na.alarismed.com> (raw)
In-Reply-To: <4n4qn3t1sj.fsf@lifelogs.com> (Ted Zlatanov's message of "16 Aug 2004 13:45:16 -0400")

"Ted Zlatanov" <tzz@lifelogs.com> writes:

> Is there a specific wishlist?

Make it faster to check for new messages and then enter a group with
new messages to see the headers. At present, when I hit 1-g to check
for new mail in one nnimap group, it sometimes takes Gnus about 10
seconds to report whether a message arrived or not (with
`nnimap-need-unselect-to-notice-new-mail' set to t). Then, if I notice
the '0' message count change to something positive, I hit enter to
select the group. Gnus then takes about ten more seconds to present a
one- or two-line Summary buffer showing the newly arrived
messages.

These nnimap groups are agentized, but I'm guessing that this slow
behavior described here involves Gnus asking the server for message
ranges and parsing the headers on new messages.

The IMAP server I use most frequently is Courier:

,----
| * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
|   THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA
|   IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready.
|   Copyright 1998-2004 Double Precision, Inc.
|   See COPYING for distribution information.
`----

I can understand the '1-g' operation taking a while, or selecting a
group to take a while, but it's painful that both take a while and
both are necessary just to see a new header in the Summary.

-- 
Steven E. Harris



  parent reply	other threads:[~2004-08-16 19:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 21:36 Mats Lidell
2004-08-11 22:05 ` Steven E. Harris
2004-08-12  2:11 ` Kevin Greiner
2004-08-12 15:13   ` Steven E. Harris
2004-08-12 15:46     ` Simon Josefsson
2004-08-12 16:08       ` Steven E. Harris
2004-08-12 16:48         ` Simon Josefsson
2004-08-12 17:26           ` Steven E. Harris
2004-08-12 19:31             ` Simon Josefsson
2004-08-16 15:02               ` Steven E. Harris
2004-08-16 15:11                 ` Steven E. Harris
2004-08-16 15:31                 ` Simon Josefsson
2004-08-16 16:45                   ` Steven E. Harris
2004-08-16 16:59                     ` Simon Josefsson
2004-08-16 17:50                       ` gnus-parameters remodeled for Topics (was: nnimap problem solved by removing .agentview and .overview) Ted Zlatanov
2004-08-16 20:03                         ` gnus-parameters remodeled for Topics Steven E. Harris
2004-08-17  3:13                   ` nnimap problem solved by removing .agentview and .overview Steven E. Harris
2004-08-17  8:23                     ` Simon Josefsson
     [not found]                       ` <ilupt5q2mwv.fsf-Hx3HMpEclzRikQyLtWShHUB+6BGkLq7r@public.gmane.org>
2004-08-17 11:59                         ` Jochen Küpper
2004-08-17 15:50                       ` Steven E. Harris
2004-08-17 16:40                         ` Simon Josefsson
2004-08-12 19:49       ` Mats Lidell
2004-08-12 20:35         ` Simon Josefsson
2004-08-20 22:09           ` Mats Lidell
2004-08-12 21:30       ` Kevin Greiner
2004-08-12 22:28         ` Simon Josefsson
2004-08-16 17:45       ` Ted Zlatanov
2004-08-16 18:34         ` Chris Green
2004-08-16 19:43           ` Steven E. Harris
2004-08-16 19:54         ` Steven E. Harris [this message]
2004-08-17 11:39         ` Steinar Bang

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=jk4wtzyoo4h.fsf@W003275.na.alarismed.com \
    --to=seh@panix.com \
    --cc=jas@extundo.com \
    /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).