From: Juri Linkov <juri@linkov.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 32607@debbugs.gnu.org
Subject: bug#32607: 27.0.50; pop-to-buffer in next-error-no-select
Date: Thu, 06 Sep 2018 01:06:34 +0300 [thread overview]
Message-ID: <8736unzjit.fsf@mail.linkov.net> (raw)
In-Reply-To: <5B8F8A1B.3030807@gmx.at> (martin rudalics's message of "Wed, 05 Sep 2018 09:47:39 +0200")
>> What is bad in user customization?
>
> That this particular one
>
> (setq display-buffer-alist '(("\\`\\*grep\\*\\'" display-buffer-same-window)))
>
> apparently doesn't do what its writer intended. This customization
> means that its writer requests to display the buffer in the selected
> window _regardless_ of whether the displayed buffer is already
> displayed anywhere else. Such a request is legitimate (think of the
> case where I am perviewing a part of a buffer in another window and I
> do not want to change that window's point) and an application should
> not override it.
This is the right customization. The intended customization is to
display the buffer in the same window, even if this buffer is already
displayed in another window: the user navigates to the needed window
and wants this buffer to appear in the selected window, not to switch to
some other window that might already display it. That's the point of
this bug report.
next prev parent reply other threads:[~2018-09-05 22:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 22:32 bug#32607: 27.0.50; pop-to-buffer in next-error-no-select Juri Linkov
2018-09-02 7:14 ` martin rudalics
2018-09-02 22:43 ` Juri Linkov
2018-09-03 7:31 ` martin rudalics
2018-09-03 22:31 ` Juri Linkov
2018-09-04 7:51 ` martin rudalics
2018-09-04 21:28 ` Juri Linkov
2018-09-05 7:47 ` martin rudalics
2018-09-05 22:06 ` Juri Linkov [this message]
2018-09-06 7:04 ` martin rudalics
2018-09-06 21:56 ` Juri Linkov
2018-09-07 6:28 ` Eli Zaretskii
2018-09-08 23:28 ` Juri Linkov
2018-09-09 5:44 ` Eli Zaretskii
2018-09-07 7:28 ` martin rudalics
2018-09-08 23:46 ` Juri Linkov
2018-09-09 8:40 ` martin rudalics
2018-09-09 16:01 ` Juri Linkov
2018-09-10 8:29 ` martin rudalics
2018-09-11 23:47 ` Juri Linkov
2018-09-12 6:33 ` martin rudalics
2018-09-12 21:47 ` Juri Linkov
2018-09-12 22:03 ` Stefan Monnier
2018-09-12 22:21 ` Juri Linkov
2018-09-12 22:06 ` Stefan Monnier
2018-09-13 7:46 ` martin rudalics
2018-09-13 11:26 ` Stefan Monnier
2018-09-13 23:04 ` Juri Linkov
2018-09-14 1:34 ` Stefan Monnier
2018-09-15 23:31 ` Juri Linkov
2018-09-16 9:09 ` martin rudalics
2018-09-16 21:19 ` Stefan Monnier
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=8736unzjit.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=32607@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 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).