From: Michael Heerdegen <michael_heerdegen@web.de>
To: 12848@debbugs.gnu.org
Subject: bug#12848: 24.2.50; Doc: give an example for a typical entry of `display-buffer-alist'
Date: Sun, 18 Nov 2012 01:55:20 +0100 [thread overview]
Message-ID: <87d2zbu3uv.fsf@web.de> (raw)
In-Reply-To: <50A65C8E.3080004@gmx.at> (martin rudalics's message of "Fri, 16 Nov 2012 16:32:30 +0100")
martin rudalics <rudalics@gmx.at> writes:
> I tried to provide an example in revision 110885 on the
> Emacs-24 release branch. Please have a look.
Thanks. I think your example is good and covers everything necessary.
It's also consistent with the code. Very good.
Only one part is a bit unclear to me, namely the last sentence of this
paragraph:
| (display-buffer
| (get-buffer-create "*foo*")
| '((display-buffer-reuse-window
| display-buffer-pop-up-window
| display-buffer-pop-up-frame)
| (reusable-frames . 0)
| (window-height . 10) (window-width . 40)))
|
| Evaluating the form above will cause `display-buffer' to proceed as
| follows: If `*foo*' already appears on a visible or iconified frame, it
| will reuse its window. Otherwise, it will try to pop up a new window
| or, if that is impossible, a new frame. If all these steps fail, it
| will try to use some existing window.
In this case, the behavior depends on `display-buffer-base-action' and
`display-buffer-fallback-action', right? Maybe we should mention that,
to make "try to use some existing window" a bit more specific.
Many thanks,
Michael.
next prev parent reply other threads:[~2012-11-18 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 22:50 bug#12848: 24.2.50; Doc: give an example for a typical entry of `display-buffer-alist' Michael Heerdegen
2012-11-09 23:00 ` Drew Adams
2012-11-16 15:32 ` martin rudalics
2012-11-18 0:55 ` Michael Heerdegen [this message]
2012-11-18 11:36 ` martin rudalics
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=87d2zbu3uv.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=12848@debbugs.gnu.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).