From: Eli Zaretskii <eliz@gnu.org>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: bug-gnu-emacs@gnu.org
Subject: bug#7296: display-pixel-height not enough
Date: Tue, 02 Nov 2010 10:53:52 -0400 [thread overview]
Message-ID: <E1PDIFE-0003AT-PL@fencepost.gnu.org> (raw)
In-Reply-To: <4CD0115D.8050008@swipnet.se> (jan.h.d@swipnet.se)
> Date: Tue, 02 Nov 2010 14:25:49 +0100
> From: "Jan D." <jan.h.d@swipnet.se>
> Cc:
>
> >> They are already implemented for X
> > Where? Maybe I misunderstood, but my impression from this discussion
> > was that they aren't and actually the need for them and their utility
> > are debatable.
> >
>
> In xterm.c, do_ewmh_fullscreen. I don't know why you say they are
> debatable
Like I said, I probably misunderstood. It's easy, what with all the
bikeshedding in this thread.
> it is the only way to correctly make an Emacs frame full
> height or full width or fullscreen or maximized. It lets the WM do the
> job, so Emacs doesn't need to count pixels and panels and taskbars and
> autohide and whatever.
I think the only practical way of doing the same on Windows is to
exclude the area reserved for the task bar. It could be that in a few
rare cases this will produce less pixels than are strictly possible.
So what are the objections to this (my original suggestion) at this
point? To be 100% clear, I suggest:
. on w32, return the dimensions sans the reserved part(s)
. on other GUI platforms, no change from the current behavior
next prev parent reply other threads:[~2010-11-02 14:53 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 10:11 bug#7296: display-pixel-height not enough Lennart Borgman
2010-10-28 18:01 ` Eli Zaretskii
2010-10-28 20:39 ` Lennart Borgman
2010-10-29 7:59 ` Eli Zaretskii
2010-10-29 8:03 ` Lennart Borgman
2010-10-29 10:12 ` Eli Zaretskii
2010-10-29 8:42 ` Lennart Borgman
2010-10-29 10:13 ` Jan Djärv
2010-10-29 10:57 ` Eli Zaretskii
2010-10-29 12:28 ` Lennart Borgman
2010-10-29 13:15 ` Jan D.
2010-10-29 13:38 ` Lennart Borgman
2010-10-29 14:51 ` Drew Adams
2010-10-29 16:53 ` Jan Djärv
2010-10-29 17:37 ` Stefan Monnier
2010-10-29 19:27 ` Lennart Borgman
2010-10-29 19:59 ` Jan D.
2010-10-29 16:24 ` Stefan Monnier
2010-10-29 19:57 ` Jan D.
2010-10-29 20:05 ` Lennart Borgman
2010-10-30 7:28 ` Jan Djärv
2010-10-30 9:25 ` Lennart Borgman
2010-10-30 10:45 ` Jan Djärv
2010-10-30 14:05 ` Lennart Borgman
2010-10-30 15:06 ` Drew Adams
2010-10-30 15:14 ` Lennart Borgman
2010-10-30 17:27 ` Jan Djärv
2010-10-30 17:41 ` Lennart Borgman
2010-10-30 18:30 ` Jan Djärv
2010-10-30 18:59 ` Lennart Borgman
2010-10-31 10:51 ` Jan Djärv
2010-10-31 12:46 ` Lennart Borgman
2010-11-01 11:37 ` Jan Djärv
2010-11-01 12:00 ` Lennart Borgman
2010-11-01 19:38 ` Jan Djärv
2010-11-01 20:26 ` Eli Zaretskii
2010-11-01 20:35 ` Lennart Borgman
2010-11-01 21:11 ` Jan Djärv
2010-11-01 21:40 ` Eli Zaretskii
2010-11-02 1:09 ` Jason Rumney
2010-11-02 4:01 ` Eli Zaretskii
2010-11-02 13:25 ` Jan D.
2010-11-02 14:53 ` Eli Zaretskii [this message]
2010-11-02 16:10 ` Lennart Borgman
2010-11-02 17:48 ` Drew Adams
2010-11-02 17:54 ` Jan Djärv
2010-10-31 3:47 ` Stefan Monnier
2010-10-31 4:13 ` YAMAMOTO Mitsuharu
2010-10-31 10:46 ` Lennart Borgman
2010-11-01 0:10 ` YAMAMOTO Mitsuharu
2010-11-01 0:24 ` Lennart Borgman
2010-11-01 0:56 ` YAMAMOTO Mitsuharu
2010-11-01 1:26 ` Lennart Borgman
2010-11-01 2:46 ` YAMAMOTO Mitsuharu
2010-11-01 10:20 ` Lennart Borgman
2010-11-01 11:40 ` Jan Djärv
2010-11-01 12:04 ` Lennart Borgman
2010-11-01 19:40 ` Jan Djärv
2010-11-02 3:45 ` YAMAMOTO Mitsuharu
2010-11-01 7:44 ` Jason Rumney
2010-11-01 10:12 ` Lennart Borgman
2010-11-01 15:09 ` Drew Adams
2010-11-01 18:08 ` Lennart Borgman
2010-11-02 14:24 ` Stefan Monnier
2010-11-02 15:24 ` Lennart Borgman
2010-11-02 17:17 ` Stefan Monnier
2010-10-31 10:53 ` Jan Djärv
2010-11-02 18:24 ` Drew Adams
2015-01-03 18:46 ` martin rudalics
2015-02-13 18:29 ` 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=E1PDIFE-0003AT-PL@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=jan.h.d@swipnet.se \
/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).