From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Shrinking mini windows to one pixel height
Date: Sat, 03 Mar 2018 12:25:27 +0200 [thread overview]
Message-ID: <83d10lv4ko.fsf@gnu.org> (raw)
In-Reply-To: <5A9A658A.5080207@gmx.at> (message from martin rudalics on Sat, 03 Mar 2018 10:06:18 +0100)
> Date: Sat, 03 Mar 2018 10:06:18 +0100
> From: martin rudalics <rudalics@gmx.at>
>
> I just noticed that one can resize mini windows down to one pixel
> which is maybe not what users want. To reproduce with emacs -Q simply
> type C-h f and drag the modeline of the only window down with the
> mouse. With some insistence you can make the minibuffer window almost
> disappear.
>
> A trivial patch is attached. I think it should go to the release
> branch but maybe the problem is too cosmetic for that.
Does the capability or making a mini window 1-pixel tall cause us any
trouble? If not, I'd prefer not to block it, let alone do that on the
release branch.
If you feel strongly about disabling this by default, on behalf of the
innocent and the naïve, I could agree with a defcustom that would do
that. Maybe.
In any case, limiting this to frame-char-height sounds too harsh to
me, because using a suitably selected font one could produce quite
legible text in the mini window of a significantly smaller size.
E.g., AFAIR sizes as small as half that don't even trigger
reallocation of the glyph matrices, because their original allocation
tolerates up to twice as many screen lines as determined by the
frame's default font.
Thanks.
next prev parent reply other threads:[~2018-03-03 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 9:06 Shrinking mini windows to one pixel height martin rudalics
2018-03-03 10:25 ` Eli Zaretskii [this message]
2018-03-03 11:28 ` martin rudalics
2018-03-03 12:03 ` Dmitry Gutov
2018-03-03 13:42 ` martin rudalics
2018-03-03 17:07 ` Drew Adams
2018-03-03 12:58 ` Eli Zaretskii
2018-03-03 13:42 ` 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=83d10lv4ko.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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).