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: Wed, 22 Jun 2011 10:13:13 +0900 [thread overview]
Message-ID: <b4m1uym7jo6.fsf@jpl.org> (raw)
In-Reply-To: 4E00C2C8.6040303@gmx.at
martin rudalics wrote:
[...]
> There was a remnant of my test settings in the default value of the
> pop-up-frame specifier: I made any new frame created this way
> unsplittable. So this is part of the behavior you see. Currently, I
> can reproduce the "display on another frame" behavior iff I make the
> selected window small enough and all other windows on this frame
> unusable. Please try once more.
What does `unusable' mean?
[...]
> If I prepend a (reuse-window nil nil nil) specifier to the first entry
> in `display-buffer-alist' the selected window gets reused (with the old
> unsplittable frame behavior).
Verified. It's not what I want, though. I only want `C-x 4 f'
to split the current window or to use the other window within
the frame as exactly the same as old Emacsen do.
That the new `display-buffer' and friends are useful is beyond
doubt, but I can imagine people will be getting flustered for
the new behavior sooner or later. For instance, someone in Japan
asked for a help last night; a frame that BBDB makes is too large,
a frame used to compose a mail is too small, etc. We can't support
all of them, can we? So, you'd better make `display-buffer-alist'
default to `conservative' or provide a switch that enables a user
to make `display-buffer' behave as before completely, I think.
BTW, shouldn't the default size of a newly created frame follow
that of `emacs -Q' or `C-x 5 2' ? I feel 80x24 is too small.
Regards,
next prev parent reply other threads:[~2011-06-22 1:13 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
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 [this message]
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=b4m1uym7jo6.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.