From: Lennart Borgman <lennart.borgman@gmail.com>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: 7296@debbugs.gnu.org
Subject: bug#7296: display-pixel-height not enough
Date: Mon, 1 Nov 2010 02:26:44 +0100 [thread overview]
Message-ID: <AANLkTimqCOSyUny7Y6j1vLkOCBtHER0p8ZoGDq+wG2m9@mail.gmail.com> (raw)
In-Reply-To: <wleib5lv4n.wl%mituharu@math.s.chiba-u.ac.jp>
On Mon, Nov 1, 2010 at 1:56 AM, YAMAMOTO Mitsuharu
<mituharu@math.s.chiba-u.ac.jp> wrote:
>>>>>> On Mon, 1 Nov 2010 01:24:55 +0100, Lennart Borgman <lennart.borgman@gmail.com> said:
>
>> Could we, as a first step, do as Eli suggested, i.e. let
>> display-pixel-height/width return the working area size instead of
>> the total display size? Is there any reason not to do this now?
>
> I'd rather suggest implementing "some of window manager emulations"
> (i.e., shortening width/height if specified one exceeds available one,
> and possibly maximized, fullwidth, and fullheight for the fullscreen
> frame parameter) on W32 and seeing if the proposed function is still
> necessary, before introducing incompatibility or new primitives.
In what way can the working display area size in pixels be
incompatible? And why is using the current total display area size
better (and more compatible)?
And how do you plan to implement the shortening without knowing what
the limits are?
next prev parent reply other threads:[~2010-11-01 1:26 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
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 [this message]
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=AANLkTimqCOSyUny7Y6j1vLkOCBtHER0p8ZoGDq+wG2m9@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=7296@debbugs.gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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).