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: Sat, 4 Jan 2014 21:47:38 +0100 [thread overview]
Message-ID: <CAAeL0SR=Pmd56U=rmNR3+Tdtr1udHH8pGCfX5PZhraBW+SYYCQ@mail.gmail.com> (raw)
In-Reply-To: <52C82BD1.1050704@gmx.at>
On Sat, Jan 4, 2014 at 4:42 PM, martin rudalics <rudalics@gmx.at> wrote:
>> Win + left arrow
>
> What does this do - move the frame to the left display border or make it
> fullheight/fullwidth?
It moves the frame to the left display border, and resizes it to
fullheight and half-width (so you can type Win+right into another
application and have the apps use the full screen side by side).
>> M-: (frame-parameter nil 'fullscreen) => nil
>> M-: (set-frame-parameter nil 'fullscreen nil)
>>
>> The frame is "restored" to a default size.
>
> Why is that bad?
Because `frame-parameter' just told us that the frame wasn't
full-anything, so setting it again to fullscreen = nil shouldn't
change it, should it? Or, alternatively, restoring the frame to its
previous size is useful, but then I would expect that, after Win+left,
(frame-parameter nil 'fullscreen) => fullheight
Which is what I said:
>> So the frame, when snapped to the left or rigth, acts like a
>> (fullscreen . fullheight) one, but it is not marked as such.
next prev parent reply other threads:[~2014-01-04 20:47 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 [this message]
2014-01-05 10:37 ` martin rudalics
2014-01-05 17:15 ` Juanma Barranquero
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAeL0SR=Pmd56U=rmNR3+Tdtr1udHH8pGCfX5PZhraBW+SYYCQ@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.