From: Stephen Berman <stephen.berman@gmx.net>
To: Robert Pluim <rpluim@gmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
Sam Steingold <sds@gnu.org>,
39344@debbugs.gnu.org
Subject: bug#39344: 28.0.50; Gnus: Selecting deleted buffer
Date: Wed, 29 Jan 2020 15:20:01 +0100 [thread overview]
Message-ID: <87k15a9wfi.fsf@gmx.net> (raw)
In-Reply-To: <m24kwegy3i.fsf@gmail.com> (Robert Pluim's message of "Wed, 29 Jan 2020 15:02:09 +0100")
On Wed, 29 Jan 2020 15:02:09 +0100 Robert Pluim <rpluim@gmail.com> wrote:
>>>>>> On Wed, 29 Jan 2020 14:56:13 +0100, Stephen Berman
> <stephen.berman@gmx.net> said:
>
> Stephen> Yes, that seems to fix the problem too.
>
> So now all we have to do is figure out why the duplicate entry is
> happening
Or forestall it in gnus-add-buffer as Andreas pondered?
> (or just apply one of the two patches and get on with our
> day :-))
BTW, gnus-kill-buffer at the end of the dolist looping over gnus-buffers
also checks buffer-live-p, apparently redundantly here (though there are
46 uses of gnus-kill-buffer and I haven't looked to see if they need the
check). But I'm afraid I have to get on with my day now, so feel free
to patch or further debug...
Steve Berman
next prev parent reply other threads:[~2020-01-29 14:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 11:48 bug#39344: 28.0.50; Gnus: Selecting deleted buffer Michael Heerdegen
2020-01-29 13:07 ` Stephen Berman
2020-01-29 13:25 ` Robert Pluim
2020-01-29 13:33 ` Stephen Berman
2020-01-29 13:42 ` Robert Pluim
2020-01-29 13:56 ` Stephen Berman
2020-01-29 14:02 ` Robert Pluim
2020-01-29 14:20 ` Stephen Berman [this message]
2020-01-29 14:40 ` Andreas Schwab
2020-01-29 13:58 ` Andreas Schwab
2020-01-29 17:00 ` Michael Heerdegen
2020-01-29 17:06 ` Sam Steingold
2020-01-30 9:23 ` Andreas Schwab
2020-01-30 16:44 ` Michael Heerdegen
2020-01-30 17:23 ` Eric Abrahamsen
2020-01-30 18:35 ` Sam Steingold
2020-01-30 18:45 ` Eric Abrahamsen
2020-02-05 11:34 ` Michael Heerdegen
2020-02-20 13:35 ` Lars Ingebrigtsen
2020-01-30 18:34 ` Sam Steingold
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k15a9wfi.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=39344@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=rpluim@gmail.com \
--cc=sds@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).