unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Thu, 23 Jun 2011 11:48:54 +0200	[thread overview]
Message-ID: <4E030C06.2070503@gmx.at> (raw)
In-Reply-To: <b4mvcvx59up.fsf@jpl.org>

 > At last I realized that my misunderstanding was due to
 > an abnormal default behavior.  I got Emacs that works never funny now.

Could you please send us the corresponding default value for
`display-buffer-alist'?  That is the thing that "never works funny" for
you written as a Lisp expression we would then use right here:

(defcustom display-buffer-alist
   '((((regexp . ".*"))
      ;; Reuse window showing same buffer on same frame.
      reuse-window (reuse-window nil same nil)
      ;; Pop up window.
      pop-up-window
      ;; Split largest or lru window.
      (pop-up-window (largest . nil) (lru . nil))
      (pop-up-window-min-height . 40) ; split-height-threshold / 2
      (pop-up-window-min-width . 80) ; split-width-threshold / 2
      ;; Reuse any but selected window on same frame.
      reuse-window (reuse-window other nil nil)
      (reuse-window-even-sizes . t)))

Thanks, martin



  reply	other threads:[~2011-06-23  9:48 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
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 [this message]
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

  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=4E030C06.2070503@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 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).