From: martin rudalics <rudalics@gmx.at>
To: Stephen Leake <stephen_leake@stephe-leake.org>, emacs-devel@gnu.org
Subject: Re: new buffer display action: display-buffer-reuse-frame
Date: Mon, 27 Jul 2015 18:03:10 +0200 [thread overview]
Message-ID: <55B6563E.7040608@gmx.at> (raw)
In-Reply-To: <86d1zebsyv.fsf@stephe-leake.org>
> I'd like to add display-buffer-reuse-frame to window.el:
This would be a misnomer. `display-buffer-reuse-window' takes a window
that already shows the buffer and `display-buffer-reuse-frames', albeit
obsolete, meant a similar thing. `display-buffer-use-some-frame' could
be used.
> This is an alternative to display-buffer-pop-up-frame. I have a couple
> of use cases for it, both based on the premise that there are normally
> two Emacs frames open. This allows other applications to temporarily
> cover one of the frames while still allowing Emacs to be in the
> foreground. It also provides another level of buffer placement control.
>
> - Using ediff to review a file for a commit. There are now three frames;
> the ediff control frame, the frame containing the old and current file
> versions under ediff control, and another frame. The user wants to put
> the log edit buffer in the other frame; they specify
> display-buffer-reuse-frame as the action, with a frame predicate that
> excludes the two ediff frames.
>
> - User would like to move a buffer to the other frame. For instance,
> they just used M-. to find the definition of an elisp function, and
> they'd like to return to the use of the function, while keeping the
> definition visible. They specify display-buffer-reuse-frame as the
> action.
>
> Thoughts?
I think you should add it (together with appropriate NEWS and elisp
manual entries).
martin
next prev parent reply other threads:[~2015-07-27 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 19:48 new buffer display action: display-buffer-reuse-frame Stephen Leake
2015-07-27 16:03 ` martin rudalics [this message]
2015-07-30 0:24 ` Stephen Leake
2015-07-30 6:00 ` martin rudalics
2015-07-30 15:24 ` Stephen Leake
2015-07-30 16:41 ` Eli Zaretskii
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=55B6563E.7040608@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=stephen_leake@stephe-leake.org \
/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).