From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: howto rollback cygwin 3.1.4-1 to older 3.0.7 version?
Date: Thu, 20 Feb 2020 10:25:00 -0000 [thread overview]
Message-ID: <20200220192439.ed2fda5cc8eb657821e4bdeb@nifty.ne.jp> (raw)
In-Reply-To: <CALEv0Pi6qEHSqEY6JLPGsUNRnaHjhKOaNXWWHB3ymWK7+QHfuw@mail.gmail.com>
On Thu, 20 Feb 2020 09:50:44 +0500
Eugene Klimov wrote:
> > > inside windows 10 (build 1909)
> > > just open WIN+R cmd.exe
> > This start cmd.exe.
> > > type
> > > `ssh root@my_redhat_entrise_linux_7.2`
> > This uses windows OpenSSH to connect linux.
> no, i install cygwin ssh package
> and i have `c:\cygwin64\bin\` in PATH environment rather than
> `c:\windows\system32\OpenSSH`
> so ssh.exe it's a cygwin process
>
> > This runs screen command in Linux.
> > Where does Cygwin's concern?
> ;) as I see it's more related to old `screen` version inside RHEL 7.2
> than cygwin concern ;(
>
> I tried to run
> `C:\Windows\System32\OpenSSH\ssh.exe root@my_rhel_72_host`
> and found bugs which look like same under Cygwin ssh, but different
> little bit ;-)
> also, I run
> `C:\Windows\System32\OpenSSH\ssh.exe -i private_key vagrant@127.0.0.1 -p 2222`
> and on my Ubuntu 18.04 screen works fine
>
> > > and view lot of bugs with wrong keys behaviors:
> > > - ctrl+space hotkey not worked (not only in `screen`, but in any cygwin executable)
> > What is your expectation by ctrl+space? This normally sends
> > ^@ (0x00) to client. Is this as you expected?
> sorry to mislead you
> I mean `ALT+SPACE`
> it's a hotkey for show window main menu
>
> > > - `left arrow`, `backspace` and `delete` keys works wrong like a `right arrow`
> > What happen if you use these keys?
> under latest cygwin 3.1.4 + ssh 8.2p1-1 behavior look like I press
> space or press "right arrow"
> https://recordit.co/thJJRbFzUp
>
> under win32 openssh behavior different
> https://recordit.co/ffAqC8BvtC
>
> under cygwin1.dll 3.0.7 and c:\cygwin64\bin\ssh.exe 8.2p1-1 behavior
> look like normal
> https://recordit.co/E0E8sfWGyY
I could reproduce your problem with screen 4.02.01 in debian
jessie.
I also found this does not occur if
vbell off
is added to .screenrc
However, this seems to be a problem in xterm emulation of
windows. So, I will make a patch (just a workaround) for this
issue.
--
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
next prev parent reply other threads:[~2020-02-20 10:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 11:04 [ANNOUNCEMENT] cygwin 3.1.4-1 Corinna Vinschen
2020-02-19 17:02 ` howto rollback cygwin 3.1.4-1 to older 3.0.7 version? Eugene Klimov
2020-02-19 18:11 ` Marco Atzeri
2020-02-19 18:43 ` Marco Atzeri
2020-02-20 4:01 ` Eugene Klimov
2020-02-20 9:13 ` Thomas Wolff
2020-02-20 9:52 ` Eugene Klimov
2020-02-20 10:31 ` Takashi Yano
2020-02-20 12:02 ` Eugene Klimov
2020-02-20 3:55 ` Eugene Klimov
2020-02-19 23:52 ` Takashi Yano
2020-02-20 4:51 ` Eugene Klimov
2020-02-20 10:25 ` Takashi Yano [this message]
2020-02-20 12:05 ` Eugene Klimov
2020-02-24 8:02 ` Houder
2020-02-19 20:30 ` mintty hangs when started from desktop shortcut (was: [ANNOUNCEMENT] cygwin 3.1.4-1) Achim Gratz
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=20200220192439.ed2fda5cc8eb657821e4bdeb@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).