From: martin rudalics <rudalics@gmx.at>
To: Roland Winkler <winkler@gnu.org>
Cc: 11985@debbugs.gnu.org
Subject: bug#11985: 24.1; fit-window-to-buffer does not grab whole frame
Date: Sat, 21 Jul 2012 13:01:20 +0200 [thread overview]
Message-ID: <500A8C00.10001@gmx.at> (raw)
In-Reply-To: <20488.13978.807457.302232@lukas.physics.niu.edu>
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
>> *** Window resizing functions.
>> A new standard function for resizing windows called `window-resize' has
>> been introduced. This and all other functions for resizing windows no
>> longer delete any windows when they become too small.
>
> This is a bit buried if one simply searches for fit-window-to-buffer e.
It was a very invasive change mainly affecting `enlarge-window' which
was called by the old `fit-window-to-buffer' (note that calling
`fit-window-to-buffer' with Emacs 23.1 could delete WINDOW itself). I
didn't go through all callers of enlarge-/shrink-buffer to check whether
they should be mentioned to.
> I got into this when I discovered that with Emacs 24.1
> Electric-pop-up-window does not behave anymore as expected. It uses
> fit-window-to-buffer for possibly grabbing the whole frame. In the
> context of what Electric-pop-up-window wants to achieve this is a
> reasonable and documented behavior.
> Possibly there is more code that relies on the old behavior.
>
> But I agree that it is probably cleaner if functions such as
> Electric-pop-up-window implement this old aspect of
> fit-window-to-buffer in some other way.
I have no strong opinion on this and never managed to understand how the
old window resize routines worked. What about the version I attached?
If necessary, I can get more aggressive ;-)
martin
[-- Attachment #2: fit-window-to-buffer.el --]
[-- Type: application/emacs-lisp, Size: 5928 bytes --]
next prev parent reply other threads:[~2012-07-21 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 6:21 bug#11985: 24.1; fit-window-to-buffer does not grab whole frame Roland Winkler
2012-07-19 10:42 ` martin rudalics
2012-07-19 16:14 ` martin rudalics
2012-07-19 16:32 ` Roland Winkler
2012-07-21 11:01 ` martin rudalics [this message]
2012-07-28 22:59 ` Roland Winkler
2012-10-06 12: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=500A8C00.10001@gmx.at \
--to=rudalics@gmx.at \
--cc=11985@debbugs.gnu.org \
--cc=winkler@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).