From: martin rudalics <rudalics@gmx.at>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 7865@debbugs.gnu.org
Subject: bug#7865: Bug in display-buffer-reuse-frames [was Re: bug#7865: 24.0.50; doc of display-buffer-reuse-frames]
Date: Sun, 13 Feb 2011 15:05:36 +0100 [thread overview]
Message-ID: <4D57E530.1080101@gmx.at> (raw)
In-Reply-To: <87aai1x8lf.fsf@stupidchicken.com>
> I think this is actually a bug. Doing `C-x b' with non-nil
> display-buffer-reuse-frames should make Emacs raise another frame if
> it;s already displaying the desired buffer---regardless of the value of
> pop-up-frames.
If `display-buffer-reuse-frames' is non-nil, Emacs currently uses an
arbitrary window on _any_ frame provided the window shows the buffer,
regardless of the value of `pop-up-frames'. It has been this way ever
since `display-buffer-reuse-frames' was introduced.
> Currently, if display-buffer-reuse-frames and pop-up-frames are both t,
> `C-x b' instead displays the buffer in the existing frame. So
> `pop-up-frames' has changed the behavior, even though it's not doing any
> "popping up" in this case.
I suppose you mean "if `display-buffer-reuse-frames' is nil and
`pop-up-frames' is t" in the first sentence above. In that case I'd
agree. But I think Stefan wants it the current way because he doesn't
care much about `display-buffer-reuse-frames' and he's using these
options for popping up dedicated frames to show some buffer in such a
frame and nowhere else. In his particular use case the present behavior
makes perfect sense because it DTRT even if he asks for displaying the
buffer when its frame _is_ currently selected.
To make `display-buffer-reuse-frames' work as you describe we'd have to
make the `get-buffer-window' routines understand as ALL-FRAMES argument
a value of say 'other, meaning to "not return a window on the selected
frame". Or, we can sort out these windows manually - you might want to
have a look at the routine `display-buffer-reuse-window' in my branch to
see how it's done there.
martin
next prev parent reply other threads:[~2011-02-13 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 16:47 bug#7865: 24.0.50; doc of display-buffer-reuse-frames Drew Adams
2011-02-12 21:10 ` bug#7865: Bug in display-buffer-reuse-frames [was Re: bug#7865: 24.0.50; doc of display-buffer-reuse-frames] Chong Yidong
2011-02-13 14:05 ` martin rudalics [this message]
2011-02-14 18:00 ` Stefan Monnier
2011-02-14 20:04 ` martin rudalics
2011-02-13 14:35 ` Drew Adams
2012-09-07 10:28 ` bug#7865: 24.0.50; doc of display-buffer-reuse-frames Chong Yidong
2012-09-07 14:11 ` Drew Adams
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=4D57E530.1080101@gmx.at \
--to=rudalics@gmx.at \
--cc=7865@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
/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.