unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 13935@debbugs.gnu.org
Subject: bug#13935: 24.3.50; `fullscreen' frame parameter is wrong, on MS Windows at least
Date: Fri, 15 Mar 2013 17:41:16 +0200	[thread overview]
Message-ID: <83obek4qn7.fsf@gnu.org> (raw)
In-Reply-To: <7BF20783B8284C1D81BF74087AF081E5@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <13935@debbugs.gnu.org>
> Date: Fri, 15 Mar 2013 08:15:24 -0700
> 
> 2. You might (dunno) also want to say that whether or not all of the described
> behavior is realized exactly as stated can depend on the window mgr.  IOW, as it
> is written now, it says that Emacs will do something, and it does not exactly do
> that in all cases.
> 
> E.g., as the bug report mentioned, the frame on MS Windows is (currently) not
> "as wide as possible".

It does that "as well as it can".

> And on Windows fullboth is not "the size of the screen"
> (because of the task bar and the width gap mentioned).

Well, if we want to go pedantic, then "the screen size" was never
formally defined.  Any reasonable definition must keep the task bar
visible, so I'd actually argue that the text is reasonably accurate.

> 3. And as I said, it certainly is possible to get fullwidth on Windows to DTRT.
> The frame-cmds.el code I pointed to uses the full screen width - no 0.5cm gap.
> (And it allows for the accessible part of the screen, e.g., lets users exclude
> or not the Windows task bar and Mac stuff - see function
> `available-screen-pixel-bounds'.)

People can use your frame-cmds.el code, until someone figures out how
to do all that on the C level and in the framework of how Emacs reacts
to changes of frame parameters.





  reply	other threads:[~2013-03-15 15:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 20:44 bug#13935: 24.3.50; `fullscreen' frame parameter is wrong, on MS Windows at least Drew Adams
2013-03-12 21:25 ` Eli Zaretskii
2013-03-12 21:59   ` Drew Adams
2013-03-15  8:30     ` Eli Zaretskii
2013-03-15  9:24       ` Dani Moncayo
2013-03-15 10:12         ` Eli Zaretskii
2013-03-15 10:26           ` Dani Moncayo
2013-03-15 13:07             ` Stefan Monnier
2013-03-15 13:48               ` Eli Zaretskii
2013-03-15 17:54                 ` Stefan Monnier
2013-03-15 12:00           ` Jan Djärv
2013-03-15 13:53             ` Eli Zaretskii
2013-03-15 18:32               ` Jan Djärv
2013-03-15 15:17           ` Drew Adams
2013-03-15 15:17         ` Drew Adams
2013-03-15 15:15       ` Drew Adams
2013-03-15 15:41         ` Eli Zaretskii [this message]
2013-03-23  9:34       ` Eli Zaretskii
2013-03-23 15:11         ` Drew Adams
2013-03-23 15:39           ` Eli Zaretskii
2013-03-12 22:38   ` Drew Adams

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=83obek4qn7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13935@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).