From: Eugene Klimov <bloodjazman@gmail.com>
To: Brian.Inglis@systematicsw.ab.ca, cygwin@cygwin.com,
takashi.yano@nifty.ne.jp, anrdaemon@yandex.ru
Subject: Re: cygwin 3.1.2 + Windows 10 Home Build 10.0.18362 - alt+space hotkeys not working
Date: Fri, 27 Dec 2019 05:00:00 -0000 [thread overview]
Message-ID: <CALEv0PhPFWuPGrech0LLxZ-72khs+ahZe3fV_rjeZd80ZpK8zg@mail.gmail.com> (raw)
In-Reply-To: <CALEv0PgsYmoVcy8qu_5NkM5Bh5HaPR7vj8ZwRMc8YVCMJzW=Qw@mail.gmail.com>
https://github.com/Maximus5/ConEmu/issues/2035
look like cygwin 3.1 and windows 1903 totally broke exists behaviors
пт, 27 дек. 2019 г. в 07:29, Eugene Klimov <bloodjazman@gmail.com>:
>
> > On 2019-12-25 23:55, Eugene Klimov wrote:
> > > when i say "works"
> > > i mean "when i press alt+space i see main menu for current window"
> > Windows apps do not normally have a main menu, they have a window management
> > menu Alt-Space and a Menu Bar Alt-... or F10
> doesn't matter how exactly we name "menu"
> i mean this menu
> https://monosnap.com/file/gBqrKZLH4zhquuNWPSTJfHRMJzlMq8
> > > windows 10 home build 18362?
> > Is this the official Windows 10 release 1903/19H1?
> yes this is Windows 10 release 1903
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-12-27 4:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 12:20 Eugene Klimov
2019-12-25 12:57 ` Takashi Yano
2019-12-25 13:33 ` Eugene Klimov
2019-12-25 14:46 ` Eugene Klimov
2019-12-25 18:46 ` Takashi Yano
2019-12-25 22:05 ` Eugene Klimov
2019-12-26 10:28 ` Andrey Repin
2019-12-26 17:45 ` Eugene Klimov
2019-12-26 19:18 ` Takashi Yano
2019-12-26 20:16 ` Brian Inglis
2019-12-27 5:00 ` Eugene Klimov
2019-12-27 5:00 ` Eugene Klimov [this message]
2019-12-27 5:29 ` Eugene Klimov
2019-12-27 12:34 ` Marco Atzeri
2019-12-27 15:04 ` Eugene Klimov
2019-12-28 13:40 ` Takashi Yano
2019-12-29 16:23 ` Brian Inglis
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=CALEv0PhPFWuPGrech0LLxZ-72khs+ahZe3fV_rjeZd80ZpK8zg@mail.gmail.com \
--to=bloodjazman@gmail.com \
--cc=Brian.Inglis@systematicsw.ab.ca \
--cc=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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.
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).