From: Tassilo Horn <tassilo@member.fsf.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 7004@debbugs.gnu.org
Subject: bug#7004: 23.2; In fullscreen mode, the echo area takes too much vertical space
Date: Thu, 17 Mar 2011 13:08:59 +0100 [thread overview]
Message-ID: <87aagueyp0.fsf@member.fsf.org> (raw)
In-Reply-To: <AANLkTinr6R=usJ12BS8SLf9TqZcAY32WsBmyWAQPw0P9@mail.gmail.com> (Dani Moncayo's message of "Thu, 9 Sep 2010 17:14:34 +0200")
Dani Moncayo <dmoncayo@gmail.com> writes:
Hi Dani,
> When I put Emacs in fullscreen mode, it seems to me that the last line
> (echo area/minibuffer) takes too much, unnecessary vertical space.
What would you expect instead?
I think, this is not an emacs problem, but it has something to do with
window managers. I'm no expert in Emacs' frame stuff or window
managers, but I think, it is something along this.
Emacs issues size hints to the window manager, which tells it the width
and height of how emacs wants to be painted. These sizes are exactly
divisible by the number of lines/columns emacs should display, which
depends on font size and stuff like that.
If the window manager honores these hints, then is it likely that a
fully maximized emacs frame (or a fullscreen frame) does not fill the
whole screen, but there is a gap of at most one line/column size in
pixels minus one pixel.
Because that somehow looks ugly, many window managers decide not to
honor hints at least for fullscreen/maximized windows. They stretch the
window to the exact display size, and then you have the effect you
describe. So you don't see one unnecessary line, but only some percent
of a unnecessary line. Even if it is 99%, it's still no full line.
IMHO, that's much better than a gap.
I know that at least there was or is a problem with emacs built with GTK
in conjunction with the KDE window manager. There, maximizing emacs did
honor the hints, and you got the gaps. But the real problem was that
the window manager would not recognize emacs as a maximized window in
that case.
Bye,
Tassilo
next prev parent reply other threads:[~2011-03-17 12:08 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 15:14 bug#7004: 23.2; In fullscreen mode, the echo area takes too much vertical space Dani Moncayo
2010-09-10 9:01 ` Jan Djärv
2010-09-10 12:39 ` Stefan Monnier
2010-09-10 14:14 ` Jan Djärv
2010-09-10 16:59 ` Andreas Schwab
2010-09-10 22:19 ` Jan Djärv
2010-09-10 22:46 ` Andreas Schwab
2010-09-11 7:37 ` Jan Djärv
2010-09-11 7:53 ` martin rudalics
2010-09-11 8:56 ` Andreas Schwab
2010-09-11 10:06 ` Jan Djärv
2010-09-11 0:10 ` David De La Harpe Golden
2010-09-11 7:50 ` Jan Djärv
2010-09-13 12:37 ` Eli Zaretskii
2010-09-13 18:59 ` Jan Djärv
2010-09-13 19:18 ` Eli Zaretskii
2010-09-13 20:48 ` Jan Djärv
2010-09-13 21:26 ` Eli Zaretskii
2010-09-14 4:48 ` Jan Djärv
2010-09-14 5:50 ` Jan Djärv
2010-09-14 7:03 ` martin rudalics
2010-09-14 17:32 ` Eli Zaretskii
2010-09-15 7:00 ` martin rudalics
2010-09-15 19:30 ` Eli Zaretskii
2010-09-15 20:45 ` Jan Djärv
2010-09-16 4:06 ` Eli Zaretskii
2010-09-16 7:35 ` Jan Djärv
2010-09-16 7:23 ` martin rudalics
2010-09-16 10:59 ` Jan Djärv
2010-09-16 12:10 ` martin rudalics
2010-09-16 13:34 ` Jan Djärv
2010-09-16 16:17 ` martin rudalics
2010-09-17 5:25 ` Jan Djärv
2010-09-17 6:34 ` martin rudalics
2010-09-17 7:09 ` Jan Djärv
2010-09-17 8:29 ` martin rudalics
2010-09-11 12:44 ` Stefan Monnier
2010-09-10 13:40 ` MON KEY
2010-09-10 16:06 ` Jan Djärv
2010-09-11 3:38 ` MON KEY
2010-12-08 13:55 ` Dani Moncayo
2011-03-16 20:13 ` bug#7004: " Dani Moncayo
2011-03-17 12:08 ` Tassilo Horn [this message]
2011-03-17 18:43 ` bug#7004: 23.2; " Dani Moncayo
2011-03-17 20:31 ` Tassilo Horn
2011-03-17 22:01 ` Dani Moncayo
2011-03-17 22:33 ` Tassilo Horn
2011-03-18 6:21 ` Jan Djärv
2011-03-18 7:30 ` Dani Moncayo
2011-03-18 7:36 ` Dani Moncayo
2011-09-05 10:32 ` bug#7004: " Dani Moncayo
2011-09-05 17:51 ` Jan Djärv
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=87aagueyp0.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=7004@debbugs.gnu.org \
--cc=dmoncayo@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).