unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 14949@debbugs.gnu.org
Subject: bug#14949: Snapped window acts like a fullscreen one (Windows 7)
Date: Sun, 05 Jan 2014 19:00:20 +0100	[thread overview]
Message-ID: <52C99DB4.4040501@gmx.at> (raw)
In-Reply-To: <CAAeL0SS6PcR_74KcPyw=iS5GfC=h0fqsoh9q1-CyRrPuSk0gkQ@mail.gmail.com>

 > No. Neither resizing the frame by hand nor using Win+left (or
 > Win+right) modifies the fullscreen frame parameter. That's what I'm
 > describing as a bug:
 >
 > Case 1:
 > emacs -Q
 > resize by hand
 > M-: (frame-parameter nil 'fullscreen) => nil
 > M-: (set-frame-parameter nil 'fullscreen nil) => nothing changes
 >
 > Case 2:
 > emacs -Q
 > Win+Left
 > M-: (frame-parameter nil 'fullscreen) => nil
 > M-: (set-frame-parameter nil 'fullscreen nil)
 >   => the pre-Win+left frame size and position is restored

But that's precisely the mystery.  It clearly indicates that Win+Left
does something different than just setting the frame size and position
and I don't have the slightest idea what that could be.

For example, if I here first evaluate

(modify-frame-parameters
  nil '((height . 61) (width . 80) (top . 0) (left . 0)))

which gives my frame the same height as FULLHEIGHT and then evaluate

(set-frame-parameter nil 'fullscreen nil)

that doesn't change anything.  Can you understand the mystery?

martin





  reply	other threads:[~2014-01-05 18:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25  0:07 bug#14949: Snapped window acts like a fullscreen one (Windows 7) Juanma Barranquero
2014-01-04 15:42 ` martin rudalics
2014-01-04 20:47   ` Juanma Barranquero
2014-01-05 10:37     ` martin rudalics
2014-01-05 17:15       ` Juanma Barranquero
2014-01-05 18:00         ` martin rudalics [this message]
2014-01-05 18:11           ` Juanma Barranquero
2014-01-05 18:39             ` 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=52C99DB4.4040501@gmx.at \
    --to=rudalics@gmx.at \
    --cc=14949@debbugs.gnu.org \
    --cc=lekktu@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).