From: Dani Moncayo <dmoncayo@gmail.com>
To: Tassilo Horn <tassilo@member.fsf.org>
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 23:01:37 +0100 [thread overview]
Message-ID: <AANLkTi=oZ4+FoPjLtgjCvEFbXTtBt7PHf=wfsS-2cYt5@mail.gmail.com> (raw)
In-Reply-To: <87mxktjxon.fsf@member.fsf.org>
Hi, Tassilo
On Thu, Mar 17, 2011 at 21:31, Tassilo Horn <tassilo@member.fsf.org> wrote:
>
> Window manager hints are nothing special about emacs:
>
I didn't say the contrary. What I wanted to say is that (with my
approach) Emacs would have no need to tell the window manager the size
it wants. Conversely, Emacs would ask to the window manager the size
of the "client area", in order to organize the layout and draw the
frame inside it.
>
> I don't see what would be the benefit of your approach. What's the
> value of being able to see half or quarter lines/columns?
>
Well, my approach is intended especially for situations in which the
GWindow is maximized or fullscreen. But maybe doesn't make much sense
when the GWindow has an arbitrary size. In such case, maybe it would
be better to resize a bit the GWindow (via hints, as you said), so
that no partial lines/columns are shown.
I don't feel very strongly about it. Indeed, sometimes I think that a
simpler solution would be to distribute the remnant space evenly
between top/bottom and left/right extremes of the "client area", so
that the emacs frame appears centered inside it.
Bye,
--
Dani Moncayo
next prev parent reply other threads:[~2011-03-17 22:01 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 ` 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 [this message]
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='AANLkTi=oZ4+FoPjLtgjCvEFbXTtBt7PHf=wfsS-2cYt5@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=7004@debbugs.gnu.org \
--cc=tassilo@member.fsf.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).