From: Dmitry Gutov <dgutov@yandex.ru>
To: martin rudalics <rudalics@gmx.at>, 36161@debbugs.gnu.org
Subject: bug#36161: 27.0.50; display-buffer-in-previous-window might choose not to use PREVIOUS-WINDOW
Date: Tue, 11 Jun 2019 16:01:11 +0300 [thread overview]
Message-ID: <1f4197c2-05b0-7ab6-41be-605eaf918200@yandex.ru> (raw)
In-Reply-To: <78fc4891-dffb-e828-baca-118a5a300c9a@gmx.at>
On 11.06.2019 11:16, martin rudalics wrote:
> > In particular, the last paragraph. When PREVIOUS-WINDOW and the selected
> > window are the same, it can select a different window, contrary to its
> > description.
>
> Right. I amended doc-string and info entry accordingly.
FWIW, emacs-26 was pretty far from my mind when I filed this.
But now I realize that we should avoid using this function in xref
either way in case we decide to distribute it on ELPA as a core package
for older Emacsen. So thanks.
> We can also change the semantics of this function to fit the old
> doc-string but I'd prefer to not do that on the release branch.
Do you know of any reasons not to do that? If only to make this function
shorter and easier to understand, that would be a good thing.
TBH, the new docstring seems a lot more confusing to me. "may override"
doesn't really tell us what the function is going to do.
next prev parent reply other threads:[~2019-06-11 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 20:29 bug#36161: 27.0.50; display-buffer-in-previous-window might choose not to use PREVIOUS-WINDOW Dmitry Gutov
2019-06-11 8:16 ` martin rudalics
2019-06-11 13:01 ` Dmitry Gutov [this message]
2019-06-12 9:18 ` martin rudalics
2019-06-12 13:31 ` Dmitry Gutov
2019-06-13 8:43 ` martin rudalics
2019-06-16 0:47 ` Dmitry Gutov
2019-06-16 8:16 ` martin rudalics
2019-06-19 1:37 ` Dmitry Gutov
2019-06-19 9:15 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f4197c2-05b0-7ab6-41be-605eaf918200@yandex.ru \
--to=dgutov@yandex.ru \
--cc=36161@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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.