Gnus development mailing list
 help / color / mirror / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Subject: Re: nnimap doing redundant work?
Date: Tue, 11 Mar 2003 12:03:16 -0500	[thread overview]
Message-ID: <uhea9deej.fsf@boost-consulting.com> (raw)
In-Reply-To: <iluof4jjpgn.fsf@latte.josefsson.org> (Simon Josefsson's message of "Mon, 10 Mar 2003 14:55:36 +0100")

Simon Josefsson <jas@extundo.com> writes:

> David Abrahams <dave@boost-consulting.com> writes:
>
>>> How do you set up the nnimap server definition in Gnus (i.e.,
>>> ~/.gnus or ~/.emacs snippet)?
>>
>> (setq gnus-select-method
>>       '(nnimap "www.stlport.com"
>>                (nnimap-address "www.stlport.com")
>>                (nnimap-stream ssl)
>>                (nnimap-authenticator login)
>>                ))
>
> Perhaps this hasn't been tested much.  Could you kill all groups,
> restart emacs with this definition instead:
>
> (setq gnus-select-method '(nnnil "")
>       gnus-secondary-select-methods '((nnimap "www.stlport.com"
>                 (nnimap-address "www.stlport.com")
>                 (nnimap-stream ssl)
>                 (nnimap-authenticator login)
>                 )))

nnimap: Updating info for nnimap+www.stlport.com:INBOX...done
Retrieving newsgroup: nnimap+www.stlport.com:INBOX...
nnimap: Updating info for nnimap+www.stlport.com:INBOX...done
Fetching headers for nnimap+www.stlport.com:INBOX...done
Generating summary...done
No more unread articles


Also, the group buffer was pretty strange after I did this; several
groups appeared multiple times.  I had to kill them and re-check my
subscriptions in order to clean things up.

> If this solves it, it is probably easy to reproduce the problem.  If
> you like to debug the lisp to see why this happens, that would be
> appreciated.

I'm very bad at elisp debugging (not very competent with edebug), but
if there's a specifc thing you want me to look at I'll be happy to do
it.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com




  reply	other threads:[~2003-03-11 17:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09 13:57 David Abrahams
2003-03-09 14:01 ` David Abrahams
2003-03-09 15:03   ` Simon Josefsson
2003-03-09 15:25     ` David Abrahams
2003-03-09 15:49       ` Simon Josefsson
2003-03-09 16:56     ` David Abrahams
2003-03-09 17:06       ` Simon Josefsson
2003-03-09 23:43         ` David Abrahams
2003-03-10  4:22         ` David Abrahams
2003-03-10 13:00           ` Simon Josefsson
2003-03-10 13:10             ` David Abrahams
2003-03-10 13:55               ` Simon Josefsson
2003-03-11 17:03                 ` David Abrahams [this message]
2003-03-11 18:00                   ` Simon Josefsson
2003-03-11 18:22                     ` David Abrahams
2003-03-12 15:29                       ` Kai Großjohann
2003-03-24  3:13                         ` David Abrahams
2003-03-13 16:00                     ` David Abrahams
2003-03-14 16:48                       ` Simon Josefsson
2003-03-17 12:21                         ` David Abrahams
2003-03-17 18:02                           ` David Abrahams
2003-03-17 18:18                             ` Simon Josefsson
2003-03-10 14:21             ` Kai Großjohann
2003-03-24  3:15               ` David Abrahams

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=uhea9deej.fsf@boost-consulting.com \
    --to=dave@boost-consulting.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).