Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: possible imap.el bug
Date: Mon, 25 Oct 2004 21:29:17 +0200	[thread overview]
Message-ID: <ilulldulhpu.fsf@latte.josefsson.org> (raw)
In-Reply-To: <4nr7nmipee.fsf@bwh.harvard.edu> (Ted Zlatanov's message of "25 Oct 2004 15:11:37 -0400")

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

> On Sun, 24 Oct 2004, jas@extundo.com wrote:
>
>> Many functions in imap.el either take a buffer argument (and switch to
>> that buffer), or assume it is in the correct buffer.  You could try to
>> track down where it is called, to see if the Gnus move code somehow
>> end up using it from the wrong buffer.
>
> Simon,
>
> I think I found the problem, the nnimap server buffer alist cleanup in
> close-server was just doing a delq to remove the server, which didn't
> work because a) strings are not necessarily eq, and b) the list was an
> association list so each element was never eq to the server name.  Now
> it iterates correctly, I think - I tested it for myself and it works
> great, and it's in CVS.  Only nnimap.el was changed.
>
> Let me know if there's problems.  I wanted to commit ASAP because it's
> an important bug fix.  It should probably go into the 5.10 branch too,
> if you approve of course.  Please look and see what you think.  I'm
> cc-ing ding again in case anyone else has comments.

It looks fine.  I wonder why it hasn't been discovered before.
Perhaps it actually will solve other hard-to-debug bug reports.

Thanks.



  reply	other threads:[~2004-10-25 19:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 18:48 Ted Zlatanov
2004-10-14 19:03 ` Simon Josefsson
2004-10-15 15:04   ` Ted Zlatanov
2004-10-15 16:39     ` Simon Josefsson
2004-10-15 16:53       ` Ted Zlatanov
2004-10-15 16:57         ` Simon Josefsson
2004-10-15 17:32           ` Ted Zlatanov
2004-10-15 17:37             ` Simon Josefsson
     [not found]               ` <4nsm8f956n.fsf@lifelogs.com>
     [not found]                 ` <iluacunx0k6.fsf@latte.josefsson.org>
     [not found]                   ` <4nsm8fcr00.fsf@bwh.harvard.edu>
     [not found]                     ` <iluvfdbrsni.fsf@latte.josefsson.org>
     [not found]                       ` <4nvfd7ubzv.fsf@lifelogs.com>
     [not found]                         ` <ilulldvoplv.fsf@latte.josefsson.org>
2004-10-25 19:11                           ` Ted Zlatanov
2004-10-25 19:29                             ` Simon Josefsson [this message]
2004-10-26 15:06                               ` Ted Zlatanov
2004-10-26 15:54                                 ` Simon Josefsson
2004-10-26 17:09                                   ` CHENG Gao
2004-10-26 17:59                                     ` Ted Zlatanov
2004-10-26 18:05                                   ` Ted Zlatanov
2004-10-26 20:07                                     ` Simon Josefsson
2004-10-26 15:51                             ` Gerd Flaig
2004-10-26 16:01                               ` Simon Josefsson
2004-10-26 16:30                                 ` Gerd Flaig

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=ilulldulhpu.fsf@latte.josefsson.org \
    --to=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).