From: Juanma Barranquero <lekktu@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 14949@debbugs.gnu.org
Subject: bug#14949: Snapped window acts like a fullscreen one (Windows 7)
Date: Sun, 5 Jan 2014 18:15:34 +0100 [thread overview]
Message-ID: <CAAeL0SS6PcR_74KcPyw=iS5GfC=h0fqsoh9q1-CyRrPuSk0gkQ@mail.gmail.com> (raw)
In-Reply-To: <52C935FA.3070205@gmx.at>
On Sun, Jan 5, 2014 at 11:37 AM, martin rudalics <rudalics@gmx.at> wrote:
> But does this mean that your Emacs also sets the fullscreen parameter to
> FULLHEIGHT when it processes the request?
No, of course not.
> I'm still too silly to understand what's going on. Let me give you a
> simple example: With emacs -Q resize your frame by dragging its borders.
> Then evaluate (set-frame-parameter nil 'fullscreen nil). Here nothing
> changes. Does anything change on your system?
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
> What happens when you remove the [...] part in w32fullscreen_hook?
Nothing different.
next prev parent reply other threads:[~2014-01-05 17:15 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 [this message]
2014-01-05 18:00 ` martin rudalics
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='CAAeL0SS6PcR_74KcPyw=iS5GfC=h0fqsoh9q1-CyRrPuSk0gkQ@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=14949@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).