From: Phil Sainty <psainty@orcon.net.nz>
To: Glenn Morris <rgm@gnu.org>
Cc: 31194@debbugs.gnu.org,
bug-gnu-emacs
<bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org>
Subject: bug#31194: 26.1; `display-buffer-in-major-side-window' was renamed without an alias.
Date: Wed, 18 Apr 2018 11:39:54 +1200 [thread overview]
Message-ID: <1d1e92f3f706ee64471a3b5fe0c04ce6@webmail.orcon.net.nz> (raw)
In-Reply-To: <1t36zt6dbs.fsf@fencepost.gnu.org>
On 2018-04-18 03:51, Glenn Morris wrote:
>> I have at least one library installed (which-key.el) which triggers an
>> error on this account.
>
> Sounds like you need to update; ref https://debbugs.gnu.org/24828#19 .
Apologies, I should have found that myself. That's certainly a
different
situation to what I had thought.
FWIW I've confirmed that the old name doesn't crop up elsewhere in my
own config.
I think that cases like this need to have NEWS entries under the
"Incompatible Lisp Changes" section? This was a function name which
was not obviously internal (no double-hyphen), so one does tend to
expect it to be documented if it no longer works (and the Changelog
entry is not addressing this aspect).
If the NEWS file mentioned the change and stated plainly that any
libraries using the old name need to be updated, I think it would
assist people who will run into this the way I did.
-Phil
next prev parent reply other threads:[~2018-04-17 23:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 13:08 bug#31194: 26.1; `display-buffer-in-major-side-window' was renamed without an alias Phil Sainty
2018-04-17 15:51 ` Glenn Morris
2018-04-17 23:39 ` Phil Sainty [this message]
2018-04-18 7:19 ` martin rudalics
2018-04-18 8:42 ` Phil Sainty
2018-04-18 8:53 ` Eli Zaretskii
2018-04-18 9:33 ` Phil Sainty
2018-04-18 12:20 ` martin rudalics
2018-04-19 0:48 ` Phil Sainty
2018-04-19 6:54 ` martin rudalics
2018-04-19 21:24 ` Juri Linkov
2018-04-19 23:49 ` Phil Sainty
2018-04-20 1:23 ` Phil Sainty
2018-04-20 6:27 ` martin rudalics
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=1d1e92f3f706ee64471a3b5fe0c04ce6@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=31194@debbugs.gnu.org \
--cc=bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org \
--cc=rgm@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).