unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "David Kågedal" <davidk@lysator.liu.se>
To: bug-gnu-emacs@gnu.org
Subject: display-buffer change
Date: Thu, 21 Jun 2007 12:11:26 +0200	[thread overview]
Message-ID: <878xadwrap.fsf@morpheus.local> (raw)

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.

To see the difference, do the following:

Split an emacs frame in two windows showing buffers A and B:

   +-------------+
   |             |
   |      A      |
   |             |
   +-------------+
   |             |
   |      B      |
   |             |
   +-------------+

While in the lower window, run

    (set-window-dedicated-p (selected-window) t)

Now, in the upper window, run

    (display-buffer "C")

In Emacs 21, this will be the result:

   +-------------+
   |      A      |
   +-------------+
   |      C      |
   +-------------+
   |             |
   |      B      |
   |             |
   +-------------+

In Emacs 22, this will be the result:

   +-------------+
   |             |
   |      C      |
   |             |
   +-------------+
   |             |
   |      B      |
   |             |
   +-------------+

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.

-- 
David Kågedal

             reply	other threads:[~2007-06-21 10:11 UTC|newest]

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

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=878xadwrap.fsf@morpheus.local \
    --to=davidk@lysator.liu.se \
    --cc=bug-gnu-emacs@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).