From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
To: martin rudalics <rudalics@gmx.at>
Cc: 37840@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#37840: Missing in the Emacs manuals:
Date: Fri, 8 Nov 2019 12:04:26 +0100 [thread overview]
Message-ID: <A2D5A4DC-9C21-4313-B007-7AFF61CA2265@univie.ac.at> (raw)
In-Reply-To: <7dd1c601-aa2c-8b44-016c-155bdd8a71eb@gmx.at>
> Am 08.11.2019 um 10:20 schrieb martin rudalics <rudalics@gmx.at>:
>
> >> This means that for Konrad's scenario to work, the minimum requirement
> >> is
> >>
> >> (custom-set-variables
> >> '(display-buffer-base-action
> >> '((display-buffer-reuse-window display-buffer-pop-up-frame)
> >> (reusable-frames . 0)))
> >> '(display-buffer-alist
> >> '(("\\*.*\\*" . (nil (inhibit-same-window . t)))))
> >> '(switch-to-buffer-obey-display-actions t))
While this works in most cases, for me it still gives a problem with Speedbar: Suppose frame A has input focus, showing buffer A. Open Speedbar via the menu. Then the Speedbar frame pops up, with input focus, but with the same layout as frame A had, and a frame B opens, with the layput intended for the Speedbar frame, but showing buffer A.
Konrad
> >
> > This doesn't look good, indeed.
> >
> > Then maybe switch-to-buffer-obey-display-actions should be replaced
> > by another variable switch-to-buffer-display-function that could be
> > customized to possible options #'pop-to-buffer-same-window,
> > #'pop-to-buffer or any other custom function (and nil by default).
>
> We can do whatever we think best as long as Emacs 27 is not out yet.
>
> If we leave things as they are we should probably mention explicitly
> that 'display-buffer-base-action' gets overridden when this option is
> set. We should also say how 'switch-to-buffer-preserve-window-point'
> is or is not respected in that case (I'm slightly confused about how
> it works now).
>
> Otherwise, I see no need for renaming the option. We could simply
> allow its value to be an ordinary display action with functions and an
> alist and have 'switch-to-buffer' act accordingly. Or am I missing
> something?
>
> martin
next prev parent reply other threads:[~2019-11-08 11:04 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 0:39 bug#37840: Missing in the Emacs manuals: Konrad Podczeck
2019-10-22 8:43 ` martin rudalics
2019-10-23 7:25 ` Konrad Podczeck
2019-10-23 7:46 ` martin rudalics
2019-10-28 17:37 ` Konrad Podczeck
2019-10-28 18:13 ` martin rudalics
2019-10-28 19:04 ` Konrad Podczeck
2019-10-29 9:28 ` martin rudalics
2019-10-30 0:56 ` Konrad Podczeck
2019-10-30 8:14 ` martin rudalics
2019-10-30 20:37 ` Konrad Podczeck
2019-10-31 7:59 ` martin rudalics
2019-11-02 21:47 ` Konrad Podczeck
2019-11-04 9:06 ` martin rudalics
2019-11-04 11:20 ` Konrad Podczeck
2019-11-04 18:27 ` martin rudalics
[not found] ` <A8BBF7A4-BFE0-44BB-BCB3-B26477FFC946@univie.ac.at>
2019-11-04 19:10 ` martin rudalics
2019-11-06 22:41 ` Juri Linkov
2019-11-07 8:39 ` martin rudalics
2019-11-07 21:58 ` Juri Linkov
2019-11-08 9:20 ` martin rudalics
2019-11-08 11:04 ` Konrad Podczeck [this message]
2019-11-08 18:27 ` martin rudalics
2019-11-08 21:12 ` Konrad Podczeck
2019-11-09 9:01 ` martin rudalics
2019-11-10 16:44 ` Konrad Podczeck
2019-11-10 18:33 ` martin rudalics
2019-11-14 10:03 ` Eli Zaretskii
2019-11-14 18:18 ` martin rudalics
2019-11-14 18:35 ` Eli Zaretskii
2019-11-15 8:50 ` martin rudalics
2019-11-22 13:09 ` Konrad Podczeck
2019-11-22 17:49 ` martin rudalics
2019-11-22 19:22 ` Eli Zaretskii
2019-11-23 1:42 ` Konrad Podczeck
2019-11-23 8:16 ` martin rudalics
2019-11-25 23:47 ` Konrad Podczeck
2019-11-26 9:32 ` martin rudalics
2019-12-02 1:35 ` Konrad Podczeck
2019-12-02 9:41 ` martin rudalics
2019-11-23 8:15 ` martin rudalics
2019-11-23 9:49 ` Eli Zaretskii
2019-11-26 9:31 ` martin rudalics
2019-11-26 9:42 ` martin rudalics
2020-09-20 11:12 ` Lars Ingebrigtsen
2019-11-10 20:11 ` Juri Linkov
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=A2D5A4DC-9C21-4313-B007-7AFF61CA2265@univie.ac.at \
--to=konrad.podczeck@univie.ac.at \
--cc=37840@debbugs.gnu.org \
--cc=juri@linkov.net \
--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).