public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eugene Klimov <bloodjazman@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygwin 3.1.2 + Windows 10 Home Build 10.0.18362 - alt+space hotkeys not working
Date: Wed, 25 Dec 2019 22:05:00 -0000	[thread overview]
Message-ID: <CALEv0Pgnc81Lm0hDbGgbNNHFL6htPQ1a-0EoToNQ4Tj374MNvA@mail.gmail.com> (raw)
In-Reply-To: <20191225223358.6de30a1e44a8af500ba13286@nifty.ne.jp>

> Uncheck the checkbox and press "save" button. This sets
> WindowsShortcuts in .minttyrc to "no".
> Then just close mintty, and restart it.
after that
alt+space not work in any cygwin console
my actions sequence
# win+r - cmd.exe
> start "mintty" mintty.exe
# click options on top-left icon, uncheck checkbox, press save, close
options, close mintty window
> start "mintty" mintty.exe
# alt+space not works
> start "mintty+bash" mintty bash
# alt+space not works
> start "mintty" mintty.exe
# click options on top-left icon, uncheck checkbox, press save, close
options, close mintty window
> start "mintty" mintty.exe
alt+space WORKS
> start "mintty+bash" mintty.exe bash
alt+space WORKS
> start "bash" bash.exe
alt+space STILL NOT WORKS

> > but when i just run bash.exe without mintty.exe, shortkeys still doesn't work
> What do you mean by "without mintty"? Do you execute bash in command
> prompt?
yes, I described how i run bash.exe above

> > > Please describe your problem in detail.
> > I try show what exactly happens on my screen
> > https://youtu.be/bO6-eihhkh4
> > when i press BACKSPACE inside screen my cursor position
> > i try install old version of mintty via setup-x86_64.exe without any effect
>
> Sorry, but I can not get what is your point. Is the problem in tab
> completion? Or cursor position problem? The "screen" means mintty
> screen? Or Gnu screen command?
screen mean "gnu screen"
and yes currently main problems is cursor positions wrong changes
inside gnu screen when i press backspace

> Takashi Yano <takashi.yano@nifty.ne.jp>
>
> --
> 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
>

--
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

  reply	other threads:[~2019-12-25 14:46 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 [this message]
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
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=CALEv0Pgnc81Lm0hDbGgbNNHFL6htPQ1a-0EoToNQ4Tj374MNvA@mail.gmail.com \
    --to=bloodjazman@gmail.com \
    --cc=cygwin@cygwin.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.
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).