unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: "David Kågedal" <davidk@lysator.liu.se>
Cc: bug-gnu-emacs@gnu.org, "Richard M. Stallman" <rms@gnu.org>
Subject: Re: display-buffer change
Date: Sat, 25 Aug 2007 09:56:08 +0200	[thread overview]
Message-ID: <46CFE098.8000607@gmx.at> (raw)
In-Reply-To: <4690AA50.1020806@gmx.at>

 > I have seen a change in Emacs 22.1 from Emacs 21 that broke my use of
 > dedicated windows.
 >
 > The problem is that (display-buffer buf) will change the contents of
 > the current window, if the other window in the frame has a dedicated
 > buffer.  In Emacs 21, a new window would be opened instead.

[...]

 > I use a dedicated small window at the bottom of my frame that always
 > contains the *compilation* buffer, and the new behaviour in Emacs 22
 > seriously lower the usability of a lots of command, such as viewing
 > diffs or showing source from gdb etc.
 >
 > I didn't find anything in NEWS that indicated that this was somehow
 > intentional.
 >

Could you please tell us whether you were able to resolve this problem.

In an earlier mail I tried to explain the new behavior as follows:

 > You should be able to handle this by customizing
 > `split-height-threshold' to a reasonable value (say 10).  Confer the
 > doc-string of `display-buffer':
 >
 >   If a full-width window on a splittable frame is available to display
 >   the buffer, it may be split, subject to the value of the variable
 >   `split-height-threshold'.
 >
 > I didn't trace what caused the behavior to change from Emacs 21 to Emacs
 > 22.  The Emacs 22 behavior is consistent with respect to the doc-strings
 > of `split-height-threshold' and `display-buffer' though.

Please tell me whether that explanation is satisfactory.

Thanks in advance.

      reply	other threads:[~2007-08-25  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 10:11 display-buffer change David Kågedal
2007-07-08  9:11 ` martin rudalics
2007-08-25  7:56   ` martin rudalics [this message]

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=46CFE098.8000607@gmx.at \
    --to=rudalics@gmx.at \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=davidk@lysator.liu.se \
    --cc=rms@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).