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: Wed, 12 Jun 2019 16:31:46 +0300 [thread overview]
Message-ID: <3415bbc7-54fd-111e-a18b-0a927d93a7b2@yandex.ru> (raw)
In-Reply-To: <d022ee9f-3038-c53a-120f-1efd44bbd3e9@gmx.at>
On 12.06.2019 12:18, martin rudalics wrote:
> > 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.
>
> OK. This time I tried to tell everything I know. Please have a look.
It's much better now, thanks. And the wording of "is usable for" is
somehow more obvious to me (even though the information is the same).
> I would have to understand first why one and the same buffer was
> displayed in different windows previously.
Not sure what answer you're looking for. Suppose a user used
switch-to-buffer sometime in the past to show it there?
I think the question is, if the caller supplies the `previous-window'
cons in ALIST, is there a point in second-guessing its choice?
FWIW, I've only found one user of this function that does that, and it's
`debug'. Which behavior do you think that command would prefer?
next prev parent reply other threads:[~2019-06-12 13:31 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
2019-06-12 9:18 ` martin rudalics
2019-06-12 13:31 ` Dmitry Gutov [this message]
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=3415bbc7-54fd-111e-a18b-0a927d93a7b2@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.