GNU bug report logs - #53910
29.0.50; context-menu-mode breaks help in read-only buffers

Previous Next

Package: emacs;

Reported by: Ergus <spacibba <at> aol.com>

Date: Thu, 10 Feb 2022 00:17:01 UTC

Severity: normal

Tags: confirmed

Fixed in version 29.0.50

Done: Juri Linkov <juri <at> linkov.net>

Bug is archived. No further changes may be made.

Full log

Message #60 received at 53910 <at> debbugs.gnu.org (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: Juri Linkov <juri <at> linkov.net>, Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi <at> gnus.org>, Ergus <spacibba <at> aol.com>,
 Drew Adams <drew.adams <at> oracle.com>,
 "53910 <at> debbugs.gnu.org" <53910 <at> debbugs.gnu.org>
Subject: Re: bug#53910: [External] : bug#53910: 29.0.50; context-menu-mode
 breaks help in read-only buffers
Date: Sat, 19 Feb 2022 10:41:09 +0100

> Maybe (kill-buffer (window-buffer <WINDOW>)) has the same effect
> when used in any window, but (bury-buffer (window-buffer <WINDOW>))
> definitely should be called in the required window, because `bury-buffer`
> uses `nil` for the WINDOW args, e.g.:
>
>        (set-window-dedicated-p nil nil)
>        (switch-to-prev-buffer nil 'bury)

I recommend against calling 'bury-buffer' in Lisp code: A function that
does

  If BUFFER-OR-NAME is nil or omitted, bury the
  current buffer.  Also, if BUFFER-OR-NAME is nil or omitted,
  remove the current buffer from the selected window if it is
  displayed there.

is clearly intended for interactive use only.

martin
This bug report was last modified 3 years and 149 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.