From: Katsumi Yamaoka <yamaoka@jpl.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: [display-buffer] a way to make it behave as before?
Date: Mon, 20 Jun 2011 19:39:54 +0900 [thread overview]
Message-ID: <b4moc1seqh1.fsf@jpl.org> (raw)
In-Reply-To: 4DFF1223.5030100@gmx.at
martin rudalics wrote:
>> I only want to see it in the other window of the current frame.
> There was a misunderstanding. I thought you wanted a new frame :-(
> In the first version of `display-buffer-alist' there was no minimum size
> of the new window specified, so you got too many windows. This should
> have been fixed in the meantime. So the best solution is probably to
> try using the default value of `display-buffer-alist' again.
I tried the new window.el without rebuilding Emacs as:
emacs -Q -eval '(makunbound (quote display-buffer-alist))' -l window
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. Isn't it strange?
At least it differs from old Emacsen.
> 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.
next prev parent reply other threads:[~2011-06-20 10:39 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 [this message]
2011-06-20 12:23 ` martin rudalics
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=b4moc1seqh1.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=emacs-devel@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.