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, 19 Jun 2019 04:37:53 +0300 [thread overview]
Message-ID: <3bf7a2d5-128e-724b-694e-908366915d3f@yandex.ru> (raw)
In-Reply-To: <85473004-8bbb-56ef-967e-0d3f8acf79ae@gmx.at>
On 16.06.2019 11:16, 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.
>
> When a different window gets used there's usually a reason. So I'd
> need a recipe to tell you more about this ...
OK, let's try again. The recipe is:
1. emacs -Q
2. Split the frame into 4 windows, so that new display-buffer calls
don't pop any new windows.
3. Select the top-left window (for instance).
4. Call M-x project-find-regexp, input "Xref", press RET. The result is
an *xref* buffer shown in one of the windows.
5. Press q.
6. Try 4. again.
7. Repeat 5,6 as many times as you like. The *xref* buffer will be
displayed in all three available windows in turn.
> > 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.
>
> An 'inhibit-same-window' entry is the canonical way to "exclude" the
> selected window. A 'previous-window' entry is just a hint to "prefer"
> some other window.
I'm not sure if you're trying to say "no" in response to my question.
But if so, I suppose this bug report can be closed (and we can conclude
that this function is definitely not suitable for xref). Thanks for
updating the docstring.
next prev parent reply other threads:[~2019-06-19 1:37 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
2019-06-16 8:16 ` martin rudalics
2019-06-19 1:37 ` Dmitry Gutov [this message]
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=3bf7a2d5-128e-724b-694e-908366915d3f@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.