all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Fix for bug #39344 (Gnus selecting deleted buffer) incomplete.
Date: Wed, 29 Jan 2020 11:57:27 -0600	[thread overview]
Message-ID: <87wo9a87so.fsf@red-bean.com> (raw)
In-Reply-To: <mvmr1zip4px.fsf@suse.de> (Andreas Schwab's message of "Wed, 29 Jan 2020 18:11:54 +0100")

On 29 Jan 2020, Andreas Schwab wrote:
>On Jan 29 2020, Karl Fogel wrote:
>
>> After some debugging, I still don't know why the bug remains, though I've
>> learned a lot about Gnus buffer management, so that's nice.  My guess is
>> that this problem is related to earlier commit 5ee3c37634f, in which many
>> functions in Gnus were changed to use `gnus-get-buffer-create' and thus
>> now store the created buffer in in `gnus-buffers'.
>
>But it adds only new buffers to gnus-buffers, so that it cannot create
>duplicates.

Well, yes, that makes sense to me too but occasionally I get surprised by an unexpected side effect in Emacs.

However, I think Sam's commit bb3b0990d really did fix bug#39344 after all.  I did a *full* rebuild this time, i.e.,

  $ make distclean && ./autogen.sh && ./configure && make bootstrap

and now the bug is gone.  Previously I had just done a plain 'make', after 'git pull' into a just-built tree had pulled down exactly that one change from Sam.  Probably the persistence of the buggy behavior was an artifact of the quick build process.

Best regards,
-Karl



      reply	other threads:[~2020-01-29 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 17:00 Fix for bug #39344 (Gnus selecting deleted buffer) incomplete Karl Fogel
2020-01-29 17:11 ` Andreas Schwab
2020-01-29 17:57   ` Karl Fogel [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=87wo9a87so.fsf@red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@suse.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.