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: Sun, 16 Jun 2019 03:47:42 +0300 [thread overview]
Message-ID: <1bf87542-fc41-98ab-c4b4-3dd0074573c1@yandex.ru> (raw)
In-Reply-To: <e909627d-1c11-0ad4-c3b9-dc5918ea4182@gmx.at>
On 13.06.2019 11:43, martin rudalics wrote:
> Hence it's more suitable for buffers popping up in special occasions
> (like, for example, when a bug occurred and the debugger should be
> entered) and less suitable for buffer editing.
I have also noticed it's not always good for special buffers either,
e.g. if I run xref-find-definitions, press q, and run it again,
different windows will be used for the two times.
> A 'previous-window' ALIST entry should continue to support the
> principle of least surprise by allowing to choose a non-selected
> window that never showed the buffer before. The selected window,
> however, should be always either chosen or excluded from choice by
> special means - either via 'display-buffer-same-window' or using an
> 'inhibit-same-window' entry.
So about that main use case (the Debugger), can it just exclude the
selected window using inhibit-same-window? That would obviate the need
for special logic in this case.
next prev parent reply other threads:[~2019-06-16 0:47 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
2019-06-13 8:43 ` martin rudalics
2019-06-16 0:47 ` Dmitry Gutov [this message]
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=1bf87542-fc41-98ab-c4b4-3dd0074573c1@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.