all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Resizing windows after display-buffer
Date: Mon, 25 Apr 2011 02:09:58 +0200	[thread overview]
Message-ID: <BANLkTi=PwiFVKVDz9JrFVP8OfZ4YWqT5bg@mail.gmail.com> (raw)
In-Reply-To: <87oc3v8b8z.fsf@stupidchicken.com>

On Mon, Apr 25, 2011 at 01:45, Chong Yidong <cyd@stupidchicken.com> wrote:

> Not long ago, we discussed generalizing temp-buffer-resize-mode so that
> it isn't just for Help buffers.  I propose doing this not with a minor
> mode, but by adding a defcustom, display-buffer-fit-window-to-buffer.

In my everyday use, I display the buffer I'm working on (code, a text
file, whatever) in a full window; the only time that the window is
split is for temporary or secondary uses; for example, help windows,
occur output, ielm, an inferior mode (python, lisp, etc.), re-builder,
bs-show, etc; and I make sure that the "secondary" buffer goes always
to the bottom window and that window is resized to fit the buffer or
have a height limit (typically about a third of the frame height). If
I switch to the bottom window and do something that would cause the
top window to display another buffer (multi-occur, for example, or
selecting a new buffer from bs-show), I *don't* want the top window to
be resized.

So, in my case, a setting that would make every display-buffer to try
to fit is much worse than a minor mode that I can call from whatever
mode hook I like.

    Juanma



  reply	other threads:[~2011-04-25  0:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-24 23:45 Resizing windows after display-buffer Chong Yidong
2011-04-25  0:09 ` Juanma Barranquero [this message]
2011-04-25  8:35   ` martin rudalics
2011-04-25 13:00     ` 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='BANLkTi=PwiFVKVDz9JrFVP8OfZ4YWqT5bg@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@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 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.