Date: Mon, 11 Sep 2017 09:03:24 +0200 From: Gary Jennejohn <gljennjohn@gmail.com> To: Mahmoud Al-Qudsi <mqudsi@neosmart.net> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: SSH from WSL acts as if overwrite were enabled while actually inserting Message-ID: <20170911090324.62f7d0aa@ernst.home> In-Reply-To: <BN6PR22MB0083E447E8D6E1E0B799266EA76B0@BN6PR22MB0083.namprd22.prod.outlook.com> References: <BN6PR22MB0083E447E8D6E1E0B799266EA76B0@BN6PR22MB0083.namprd22.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 10 Sep 2017 15:56:14 +0000 Mahmoud Al-Qudsi <mqudsi@neosmart.net> wrote: > Hello all, > > Sorry about the confusing subject line, it___s the best I could think of to succinctly summarize the issue at hand. I___ve been running into an issue with FreeBSD from 10.x to 12-CURRENT and wanted to check with the mailing list before I bugged it to make sure it is a FreeBSD bug and not a WSL (the new Linux subsystem for Windows) bug. > > When I ssh into a FreeBSD host from a TERM=xterm-256color host that has no problem SSHing into Linux machines, the following behavior is observed (regardless of the $TERM value under FreeBSD or the SSH shell I___m logging into). > > Imagine the prompt currently reads as follows with the cursor at the space denoted by _ in the text below: > > user@freebsd % foo_bar > > If I type in ` foo` at this point, the prompt now reads > > user@freebsd % foo foo_ > > However, the _actual_ contents of the prompt are really > > user@freebsd % foo foo bar_ > > i.e. the _displayed_ prompt acted as if OVERWRITE were on, but the actual behavior is that INSERT was enabled. The actual behavior is the expected behavior, which is what the prompt should have shown. > > I do not experience this behavior when using, say, Putty instead of OpenSSH under WSL. I also do not experience this behavior when SSHing into a non-FreeBSD host. > > If this is not a FreeBSD bug, I___ll raise it with the WSL team who have proven to be very earnest in their attempts at fixing all compatibility issues via their GitHub presence. > > (A screenshot of the observed behavior, if it helps: http://i.imgur.com/k6hVtbQ.png ) > Have you tried it with a different shell? Such as /bin/sh rather than fish? -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170911090324.62f7d0aa>