From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39072@debbugs.gnu.org, Corwin Brust <corwin@bru.st>
Subject: bug#39072: 26.3; Pressing C-z in fullscreen messes all frames
Date: Fri, 10 Jan 2020 13:47:35 -0500 [thread overview]
Message-ID: <85muavf8s8.fsf@gmail.com> (raw)
In-Reply-To: <83sgkn88fh.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Jan 2020 20:37:06 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Corwin Brust <corwin@bru.st>
>> Date: Fri, 10 Jan 2020 11:01:54 -0600
>>
>> # windows 10, GNU Emacs 26.3 (msi)
>> emacs -Q
>> F-11 ;;now we're full-screen
>> C-z ;; now all frames are "locked"
>>
>> ...
>>
>> At this point, emacs won't accept keyboard input. C-g doesn't do anything,
>> If there are several frames they will all be in this state. We seem to be able to
>> recover using the mouse to execute an interactive command. In fact, I was
>> able to use Help | Send Bug Report to create this message *after* reproducing
>> from my -Q session -- once the mini-buffer prompt popped I was able to type
>> again.
>
> I cannot reproduce this, but I'm not on Windows 10. On my Windows
> system, C-z minimizes the frame, even if it was previously maximized
> with F11.
I have a Windows 10 box, and I can't reproduce it either.
In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32)
of 2019-08-29 built on CIRROCUMULUS
Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd
Windowing system distributor 'Microsoft Corp.', version 10.0.17763
Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Configured using:
'configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install 'CFLAGS=-O2 -static -g3''
next prev parent reply other threads:[~2020-01-10 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 17:01 bug#39072: 26.3; Pressing C-z in fullscreen messes all frames Corwin Brust
2020-01-10 18:37 ` Eli Zaretskii
2020-01-10 18:47 ` Noam Postavsky [this message]
2020-01-10 20:35 ` Corwin Brust
2020-01-10 21:10 ` Eli Zaretskii
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=85muavf8s8.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=39072@debbugs.gnu.org \
--cc=corwin@bru.st \
--cc=eliz@gnu.org \
/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).