unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 16340@debbugs.gnu.org
Subject: bug#16340: 24.3.50; Maximize to the left/right side of the screen (on Windows 7 & 8)
Date: Mon, 06 Jan 2014 20:58:47 +0100	[thread overview]
Message-ID: <52CB0AF7.8010304@gmx.at> (raw)
In-Reply-To: <CAH8Pv0j-3A6=p1LjD9nmaPAC_7J=_tSr4xZH_x32QvGyBZzPcg@mail.gmail.com>

 > Ok: the new frame I create after setting 'frame-resize-pixelwise' to
 > 't' doesn't have the problem reported in this bug, i.e. that frame
 > fits exactly in the left/right half of the screen when I do "windows
 > key" + "left/right arrow".

So all I can say is that Windows obeys your size hints.  If you can live
with pixelwise resized frames (I do so for almost a year now) continue
to do so.  Otherwise you have to live with the gaps.  Tertium non datur.

 >> And please tell me the values of (frame-parameter nil 'fullscreen)
 >> before, during and after you left the "maximized to the left" state.
 >
 > '(frame-parameter nil 'fullscreen)' returns 'nil' before, during and
 > after the "maximization to the left".

Thanks.  This confirms what Juanma told me earlier.

martin





  reply	other threads:[~2014-01-06 19:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-04 18:58 bug#16340: 24.3.50; Maximize to the left/right side of the screen (on Windows 7 & 8) Dani Moncayo
2014-01-05 10:37 ` martin rudalics
2014-01-06 19:34   ` Dani Moncayo
2014-01-06 19:58     ` martin rudalics [this message]
2014-01-06 20:56       ` Dani Moncayo
2014-01-06 22:03         ` martin rudalics
2014-01-06 22:16           ` Dani Moncayo
2014-01-06 23:04             ` Juanma Barranquero
2014-01-07  7:08               ` Dani Moncayo
2014-01-07 10:19                 ` martin rudalics
2014-01-07 10:19               ` martin rudalics
2014-01-07 10:18             ` martin rudalics
2014-01-07  1:10           ` Daniel Colascione
2014-01-07 10:19             ` martin rudalics
2014-01-07 13:42               ` Stephen Berman
2014-01-07 17:31                 ` martin rudalics
2014-01-07 19:50                   ` Stephen Berman
2014-01-11 10:24                     ` martin rudalics
2014-01-07 17:36             ` 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=52CB0AF7.8010304@gmx.at \
    --to=rudalics@gmx.at \
    --cc=16340@debbugs.gnu.org \
    --cc=dmoncayo@gmail.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).