From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
To: martin rudalics <rudalics@gmx.at>
Cc: 37840@debbugs.gnu.org
Subject: bug#37840: Missing in the Emacs manuals:
Date: Mon, 4 Nov 2019 12:20:11 +0100 [thread overview]
Message-ID: <FF988297-ED94-4EBB-8ACA-A6E4EF9024A7@univie.ac.at> (raw)
In-Reply-To: <438c4dfa-f7c2-5f5e-32bc-eafdd7c33cb7@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 2386 bytes --]
> Am 04.11.2019 um 10:06 schrieb martin rudalics <rudalics@gmx.at>:
>
> > Suppose, without any display-buffer-alist customization, I have just
> >
> > (setq display-buffer-base-action
> > (quote (
> > (display-buffer-reuse-window display-buffer-pop-up-frame)
> > (reusable-frames . x)
> > )))
> >
> > in my init file, where x can be any of 0,1, nil, visible, all these
> > choices don’t matter for this: If I open Emacs, the initial frame
> > shows up, and any file loaded via recent-files, or by dragging on
> > the Emacs icon, or by clicking on the file icon, shows up in the
> > initial frame, contrary to what is advertised in the
> > manual.
>
> What _is_ advertised in the manual?
To quote from Section 28.13.5:
Let's consider a user who, as a rule, prefers to display buffers on another frame. Such a user might provide the following customization:
(customize-set-variable
'display-buffer-base-action
'((display-buffer-reuse-window display-buffer-pop-up-frame)
(reusable-frames . 0)))
This setting will cause display-buffer to first try to find a window showing the buffer on a visible or iconified frame and, if no such frame exists, pop up a new frame.
The words “another” and “new” suggest a behavior different from what I described above.
>
> > However, once a file is loaded, then re-selecting it via
> > Menu->Buffers, pops it up in a new frame (with properties as
> > specified in defaults-frame-alist). So, what is the relation between
> > "display-buffer-base-action” and “default-frame-alist”?
>
> If a new frame is created by 'display-buffer', its parameters are
> determined by
>
> (1) any 'pop-up-frame-parameters' entry found,
>
> (2) the value of 'pop-up-frame-alist' (if the function specified by
> 'pop-up-frame-function' processes it - the default does) and
>
> (3) the value of 'default-frame-alist'.
>
> So if you use the 'display-buffer-base-action' specification from the
> top, only 'default-frame-alist' will be used because you neither
> customized any 'pop-up-frame-parameters' nor 'pop-up-frame-alist' (the
> latter should not be used anyway). All based on the assumption that
> you have customized 'switch-to-buffer-obey-display-actions' so that
> Menu->Buffers indeed tries to pop to the buffer.
>
> martin
>
[-- Attachment #2: Type: text/html, Size: 4466 bytes --]
next prev parent reply other threads:[~2019-11-04 11:20 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 [this message]
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
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=FF988297-ED94-4EBB-8ACA-A6E4EF9024A7@univie.ac.at \
--to=konrad.podczeck@univie.ac.at \
--cc=37840@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).