emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#24828: closed (26.0.50; Renaming of display-buffer


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#24828: closed (26.0.50; Renaming of display-buffer-in-major-side-window broke which-key.el)
Date: Mon, 31 Oct 2016 18:24:01 +0000

Your message dated Mon, 31 Oct 2016 19:23:44 +0100
with message-id <address@hidden>
and subject line Re: bug#24828: 26.0.50; Renaming of 
display-buffer-in-major-side-window broke which-key.el
has caused the debbugs.gnu.org bug report #24828,
regarding 26.0.50; Renaming of display-buffer-in-major-side-window broke 
which-key.el
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24828: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24828
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 26.0.50; Renaming of display-buffer-in-major-side-window broke which-key.el Date: Sun, 30 Oct 2016 19:21:05 +0100
As the subject says. Maybe an alias is in order?

I don't know if there are more cases like this.


In GNU Emacs 26.0.50.1 (x86_64-pc-linux-gnu, X toolkit)
 of 2016-10-21 built on qcore
Repository revision: 0929e061fb544c0f4c10ff0412a41cf7e8148270
Windowing system distributor 'The X.Org Foundation', version 11.0.11804000
System Description:     Ubuntu 16.10



--- End Message ---
--- Begin Message --- Subject: Re: bug#24828: 26.0.50; Renaming of display-buffer-in-major-side-window broke which-key.el Date: Mon, 31 Oct 2016 19:23:44 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)
which-key.el was "fixed" with the following commit message:

 Remove use of display-buffer-in-major-side-window

 According to emacs bug #24828, this is an internal function and should
 not be used. Following the advice from that report, switch to
 display-buffer-in-side-window and add an option for the user to specify
 the slot value for that function.

Closing this bug. Let's hope that there are no more packages out there
that use this function(s).


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]