From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 11276@debbugs.gnu.org
Subject: bug#11276: minibuffers windows can no longer explictly be resized
Date: Thu, 19 Apr 2012 17:37:58 +0300 [thread overview]
Message-ID: <83zka7iy7t.fsf@gnu.org> (raw)
In-Reply-To: <4F8FEBFE.2030404@gmx.at>
> Date: Thu, 19 Apr 2012 12:42:06 +0200
> From: martin rudalics <rudalics@gmx.at>
> Cc: 11276@debbugs.gnu.org
>
> First bug. I forgot that one can invoke `enlarge-window' and
> `shrink-window' in the minibuffer window. I'm not sure though whether these
> should have any effect when `resize-mini-windows' is non-nil.
For compatibility with previous versions of Emacs, I think it
shouldn't, at least not on the emacs-24 branch.
resize-mini-windows is a misnomer: it actually means "mini-window size
is controlled by display engine". That's why window-sizing commands
in previous versions never paid heed to it, only redisplay did. And
that's why, quite counter-intuitively, setting it to _nil_ allows the
user to resize the mini-window.
We could make the implementation more in line with the name in future
versions, if we want, of course.
next prev parent reply other threads:[~2012-04-19 14:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 1:04 bug#11276: minibuffers windows can no longer explictly be resized Glenn Morris
2012-04-19 6:56 ` martin rudalics
2012-04-19 7:12 ` Glenn Morris
2012-04-19 10:42 ` martin rudalics
2012-04-19 14:37 ` Eli Zaretskii [this message]
2012-04-19 15:13 ` Drew Adams
2012-04-19 17:18 ` martin rudalics
2012-04-20 7:43 ` Eli Zaretskii
2012-04-20 10:01 ` martin rudalics
2012-04-20 10:16 ` Eli Zaretskii
2012-04-21 1:01 ` Glenn Morris
2012-04-19 14:31 ` Eli Zaretskii
2012-04-19 17:23 ` martin rudalics
2012-04-20 7:47 ` Eli Zaretskii
2012-04-20 10:01 ` martin rudalics
2012-04-20 10:49 ` Eli Zaretskii
2012-04-20 12:05 ` martin rudalics
2012-04-20 14:17 ` Eli Zaretskii
2012-04-20 15:31 ` martin rudalics
2012-04-19 14:28 ` Eli Zaretskii
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=83zka7iy7t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11276@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).