From: martin rudalics <rudalics@gmx.at>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-devel@gnu.org
Subject: Re: [display-buffer] a way to make it behave as before?
Date: Mon, 20 Jun 2011 14:23:04 +0200 [thread overview]
Message-ID: <4DFF3BA8.3070007@gmx.at> (raw)
In-Reply-To: <b4moc1seqh1.fsf@jpl.org>
> emacs -Q -eval '(makunbound (quote display-buffer-alist))' -l window
If you make this unbound, you ignore the default values which are
responsible for implementing the traditional behavior.
> The *scratch* window appears in an Emacs frame. Say it is the
> first frame. Type `C-x 5 b RET' there. The *Messages* window
> will appear in a new Emacs frame. Say it is the second frame.
> And then type `C-x 4 f ~/.emacs RET' in the second frame. Hmm,
> the .emacs window appears in the first frame.
With emacs -Q the *Messages* window is split here. When
`display-buffer-alist' is unbound it uses a fallback method, which,
since you implicitly removed the window splitting part, reuses any
window but the selected one.
> At least it differs from old Emacsen.
It shouldn't for emacs -Q. And in this regard you're right. I
remembered that someone wanted to change the default value of
`display-buffer-reuse-frames' to t and have set the default value of
`display-buffer-alist' accordingly. That's what you've seen earlier
(but not in the scenario above!). I'll take that back. Meanwhile, try
the steps below which will anticipate my change and tell me whether it
works.
>> If you want to avoid that another frame showing the buffer already is
>> used, replace in all reuse-window specifiers you find in
>> `display-buffer-alist' the last element by nil.
>
>> That is, wherever you see an object like
>
>> (reuse-window nil same visible)
>
>> replace the term `visible' by nil
>
>> (reuse-window nil same nil)
>
>> so only the selected and not all visible frames get inspected.
>
> I'll try it. Thanks.
Thank you, martin
next prev parent reply other threads:[~2011-06-20 12:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 9:54 [display-buffer] a way to make it behave as before? Katsumi Yamaoka
2011-06-17 15:47 ` martin rudalics
2011-06-20 5:39 ` Katsumi Yamaoka
2011-06-20 6:21 ` Katsumi Yamaoka
2011-06-20 9:25 ` martin rudalics
2011-06-20 10:39 ` Katsumi Yamaoka
2011-06-20 12:23 ` martin rudalics [this message]
2011-06-20 23:04 ` Katsumi Yamaoka
2011-06-21 2:11 ` Katsumi Yamaoka
2011-06-21 14:05 ` Katsumi Yamaoka
2011-06-21 16:11 ` martin rudalics
2011-06-22 1:13 ` Katsumi Yamaoka
2011-06-22 7:20 ` martin rudalics
2011-06-22 13:32 ` Katsumi Yamaoka
2011-06-22 13:45 ` martin rudalics
2011-06-22 14:32 ` Drew Adams
2011-06-22 14:59 ` joakim
2011-06-23 5:07 ` Miles Bader
2011-06-22 16:43 ` Thierry Volpiatto
2011-06-23 6:40 ` Katsumi Yamaoka
2011-06-23 9:48 ` martin rudalics
2011-06-23 10:21 ` Katsumi Yamaoka
2011-06-23 11:08 ` martin rudalics
2011-06-23 11:52 ` David Kastrup
2011-06-22 15:13 ` Juanma Barranquero
2011-06-22 23:20 ` Katsumi Yamaoka
2011-06-23 0:23 ` Juanma Barranquero
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=4DFF3BA8.3070007@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=yamaoka@jpl.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 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.