all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: MON KEY <monkey@sandpframing.com>
To: 7004@debbugs.gnu.org
Subject: bug#7004: 23.2; In fullscreen mode, the echo area takes too much vertical space
Date: Fri, 10 Sep 2010 09:40:36 -0400	[thread overview]
Message-ID: <AANLkTikAokxUTjqCqUNEoDtkuf-N_84P7hMWthpeo5Ow@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinr6R=usJ12BS8SLf9TqZcAY32WsBmyWAQPw0P9@mail.gmail.com>

,----
| From your picture:
| The height of tool bar + menu bar is 73 pixels.
| Your font height is 17 pixels.
| (1024 - 73)/17 = 55.94117
`----

But, it can also happen when the tool-bar/menu-bar aren't displayed.
Shouldn't the display calculations take this into consideration?

,----
| The remnant (0.94117) is just wasted space, no whole line can be
made to fit in
| to it so it shows up at the botton as unused space. Any window
height that isn't
| an integral of the font height will show like this.
|
| There is no bug here,
`----

It certainly isn't a feature!
I find it can render fullscreen usage aesthetically untenable.

FWIW I've had to tweak X to get (somewhat) satisfactory fullscreen behaviour.

--
/s_P\





  parent reply	other threads:[~2010-09-10 13:40 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 [this message]
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 ` bug#7004: 23.2; " Tassilo Horn
2011-03-17 18:43   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikAokxUTjqCqUNEoDtkuf-N_84P7hMWthpeo5Ow@mail.gmail.com \
    --to=monkey@sandpframing.com \
    --cc=7004@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.