Gnus development mailing list
 help / color / mirror / Atom feed
From: Mark Plaksin <happy@usg.edu>
Subject: Re: nnimap: Server buffer vs secondary-select-methods
Date: Fri, 04 Feb 2005 16:44:50 -0500	[thread overview]
Message-ID: <m3wttovw31.fsf@water.tss.usg.edu> (raw)
In-Reply-To: <uvf98ayvd.fsf@boost-consulting.com>

David Abrahams <dave@boost-consulting.com> writes:

> Mark Plaksin <happy@mcplaksin.org> writes:
>

...

>> I have always struggled to understand the difference between using the
>> Server buffer and using gnus-secondary-select-methods.  Today I made Gnus a
>> zillion times (no exaggeration :) faster by finally putting my IMAP servers
>> into gnus-secondary-select-methods.
>
> Hmm, my imap server is my primary select method, and my Gnus could
> stand to get a zillion times faster.  Do I have to make it a secondary
> select method also?

I don't know about that.  After making my change, this is all that appears
in *Messages* when I check mail (assuming the IMAP servers are already open):

  Checking new news...
  Opening nnimap server on 1pof...done
  nnimap: Checking mailboxes...done
  Opening nnimap server on bor...done
  nnimap: Checking mailboxes...done
  Checking new news...done

Before I had a line (or three) for every single folder.

The key seems to have been getting (and keeping) the short name for my IMAP
server into what I see with G E in the Group buffer.  In the example G E
output below, it just has "bor" as the server name instead of
"nnimap+bor...".  I wasn't able to get that to stick until my IMAP servers
were secondary select methods.  I never tried making one of them the
primary select method.

G E output:
("nnimap+bor:Mail/bugzilla" 3
 "bor"
 ((uidvalidity . "1100103011")
  (timestamp 16899 59047)
  (total-expire . t)))





      reply	other threads:[~2005-02-04 21:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30 16:45 Mark Plaksin
2005-02-04 19:50 ` David Abrahams
2005-02-04 21:44   ` Mark Plaksin [this message]

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=m3wttovw31.fsf@water.tss.usg.edu \
    --to=happy@usg.edu \
    /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).