From: martin rudalics <rudalics@gmx.at>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 6385@debbugs.gnu.org
Subject: bug#6385: A slightly less aggressive fit-window-to-buffer
Date: Sun, 13 Jun 2010 19:44:58 +0200 [thread overview]
Message-ID: <4C15191A.50009@gmx.at> (raw)
In-Reply-To: <AANLkTinnRS6R6zalMDLToPYIuK9IU-z1Bh66EouumJq-@mail.gmail.com>
> I think it is very practical to be able to do let-bind
> window-min-height this way. I can look at the code of course and found
> out, but where is is possible deleting of small height windows done?
With the first call to delete_window in enlarge_window. This deletes
the argument window if its new size is less than `window-min-height'.
And size_window calls delete_window on any window whose size has become
too small when (virtually) resizing a parent window back to its original
size.
> Is there a thought behind it or is it a bug?
The thought behind it was probably that anyone who wants to enlarge a
window also accepts that other windows may get deleted in the process.
I suppose "collateral damage" has become the terminus technicus for such
behavior.
martin
next prev parent reply other threads:[~2010-06-13 17:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 18:56 bug#6385: A slightly less aggressive fit-window-to-buffer Lennart Borgman
2010-06-11 13:21 ` martin rudalics
2010-06-11 17:15 ` Lennart Borgman
2010-06-12 8:00 ` martin rudalics
2010-06-12 13:03 ` Lennart Borgman
2010-06-12 14:16 ` martin rudalics
2010-06-12 14:24 ` Lennart Borgman
2010-06-13 7:51 ` martin rudalics
2010-06-13 15:23 ` Lennart Borgman
2010-06-12 15:21 ` Drew Adams
2010-06-13 7:51 ` martin rudalics
2010-06-13 12:39 ` Drew Adams
2010-06-13 14:34 ` martin rudalics
2010-06-13 15:20 ` Lennart Borgman
2010-06-13 17:44 ` martin rudalics [this message]
2010-06-13 17:48 ` Lennart Borgman
2010-06-13 16:33 ` Drew Adams
2010-06-13 17:45 ` martin rudalics
2010-06-13 18:21 ` Drew Adams
2010-06-13 20:04 ` Stefan Monnier
2010-06-14 6:49 ` martin rudalics
2010-06-14 6:57 ` Drew Adams
2011-10-11 9:31 ` 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=4C15191A.50009@gmx.at \
--to=rudalics@gmx.at \
--cc=6385@debbugs.gnu.org \
--cc=lennart.borgman@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 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).