all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: shrink-window-if-larger-than-buffer in VC-diff
Date: Sun, 15 Aug 2010 23:10:07 -0400	[thread overview]
Message-ID: <87iq3bs168.fsf@stupidchicken.com> (raw)
In-Reply-To: <AANLkTik24xC=NhGPsk0TOrweG68RHU+sUMV4uBq3N=q+@mail.gmail.com> (Juanma Barranquero's message of "Mon, 16 Aug 2010 00:44:35 +0200")

Juanma Barranquero <lekktu@gmail.com> writes:

>> I think the shrink-window-if-larger-than-buffer call in vc-diff-finish
>> shouldn't be there in the first place.  It's well-intentioned, but even
>> in cases less extreme that the above, it can be annoying to resize the
>> user's windows.  Any objection to removing this call?
>
> IMHO, such cases should be made optional (perhaps a global variable
> covering such uses in many/most/all modes?) instead of removed. I
> usually *always* want the shrinking behavior, and rarely reuse the
> window.

As far as I can tell, the only really good uses of s-w-i-l-t-b occur
when the window in question is electric.  For permanent windows, the
behavior seems poor.  Here is another example of it misbehaving, in
finder:

1. M-x finder-by-keyword RET
2. C-x 1
3. Go to "tex" and type RET
4. Go to "tex-mode.el" and RET

   => The upper window, now showing *Finder-package* with an empty
   commentary, is 4 lines tall (due to s-w-i-l-t-b).

5. C-x o
6. Go to "reftex.el" and RET

   => The upper window now shows *Finder-package* with a long verbose
   commentary.  But it is still 4 lines tall, and therefore useless.


I think the existing non-electric uses of s-w-i-l-t-b need to be
reconsidered.  Maybe we should change `pop-to-buffer' so that it accepts
an option to both shrink *and* grow windows.  Then people who want their
windows to resize automagically can use this option, and have it work
more reliably than it does now.  (The default should be to avoid
resizing at all.)



  reply	other threads:[~2010-08-16  3:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-14 23:15 shrink-window-if-larger-than-buffer in VC-diff Chong Yidong
2010-08-15  1:14 ` Miles Bader
2010-08-15  7:07 ` Andreas Schwab
2010-08-15  9:38 ` annoyances [Was: shrink-window-if-larger-than-buffer in VC-diff] Uday S Reddy
2010-08-15 10:06   ` annoyances David Kastrup
2010-08-15 10:33     ` annoyances Uday S Reddy
2010-08-15 14:12   ` annoyances [Was: shrink-window-if-larger-than-buffer in VC-diff] Stephen J. Turnbull
2010-08-15 18:35     ` Uday S Reddy
2010-08-16  1:45       ` Stephen J. Turnbull
2010-08-16  8:54         ` Uday S Reddy
2010-08-15 22:44 ` shrink-window-if-larger-than-buffer in VC-diff Juanma Barranquero
2010-08-16  3:10   ` Chong Yidong [this message]
2010-08-16 23:06     ` Juanma Barranquero
2010-08-18 21:53       ` Chong Yidong
2010-08-20  9:06         ` martin rudalics
2012-10-27 13:45     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iq3bs168.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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.