From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 12648@debbugs.gnu.org
Subject: bug#12648: 24.2.50; display-buffer switches to another frame
Date: Sun, 14 Oct 2012 21:28:59 +0200 [thread overview]
Message-ID: <83zk3o4zus.fsf@gnu.org> (raw)
In-Reply-To: <507B0590.3020402@gmx.at>
> Date: Sun, 14 Oct 2012 20:33:52 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: 12648@debbugs.gnu.org
>
> > emacs -Q
> > C-x b foo
> > C-x 5 b bar
> >
> > Now you have 2 frames, one displays the buffer "foo", the other
> > displays the buffer "bar" and is the selected frame.
> >
> > M-: (display-buffer "foo" nil 'visible) RET
> >
> > This quite unexpectedly selects the frame which displays "foo". But
> > display-buffer is not supposed to select the window where it displays
> > the buffer.
>
> Unless it appears on another frame.
Isn't that difference confusing?
> If with emacs -Q you do
>
> (let ((pop-up-frames t))
> (display-buffer (get-buffer-create "baz")))
>
> that buffer is shown on a new frame and its window is selected.
I think this is different: setting pop-up-frames non-nil expresses a
wish to see certain behavior that the default shouldn't have.
> > http://lists.gnu.org/archive/html/help-gnu-emacs/2012-10/msg00188.html
> >
> > for the original complaint.
>
> Maybe we should provide an alist entry like select-frame for this. If
> the buffer already appears in another frame, we would select the frame
> only if the entry is set. If a new frame is created, we could try to
> not select it if the entry is not set and the window manager supports
> creating a frame and not selecting it.
Yes, but is the current behavior useful as it is?
If gud.el should call display-buffer in some different way to avoid
selecting the frame with the source, that, too, could be a good
solution.
next prev parent reply other threads:[~2012-10-14 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 16:49 bug#12648: 24.2.50; display-buffer switches to another frame Eli Zaretskii
2012-10-14 18:33 ` martin rudalics
2012-10-14 19:28 ` Eli Zaretskii [this message]
2012-10-15 12:52 ` martin rudalics
2012-10-15 17:26 ` Eli Zaretskii
2012-10-16 9:39 ` martin rudalics
2012-10-16 13:27 ` Stefan Monnier
2012-10-17 9:37 ` martin rudalics
2012-10-18 19:46 ` Chong Yidong
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=83zk3o4zus.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12648@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.