-
Notifications
You must be signed in to change notification settings - Fork 768
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vi on Linux turns console text blue #1203
Comments
Windows openssh client uses console support (conhost.exe) for parsing the incoming ANSI stream. Looks like the latest windows OS has fixed it. I verified this on windows Version 10.0.17134.112. |
Out of the dozen or so times I have used vi this has happened once. What is very annoying is that the color change persists after exiting the ssh session. Ultimately I restarted the PS console. Client Info Server Info |
Please try the new windows 10 fall update (https://support.microsoft.com/en-us/help/4464619) |
fyi, Just realized the windows 10 fall update is paused because of some known issues. |
This remains an issue for me: Edition: Windows 10 Enterprise |
"OpenSSH for Windows" version
(Will fill in when I get home later, sorry! Leaving command here for reference)
((Get-Item (Get-Command sshd).Source).VersionInfo.FileVersion)
Server OperatingSystem
CentOS 7.5.1804
Client OperatingSystem
Windows 10
(Will fill in with more complete info when I get home later, sorry! Leaving command here for reference)
((Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows nt\CurrentVersion\" -Name ProductName).ProductName)
What is failing
When executing
vi
for a new file or seemingly at random on a fresh install of CentOS 7, the console text default color seems to be changed to blue, i.e. all text not colored by syntax highlighting invi
is blue, and any text the console generates henceforth which isn't preceded by an ANSI terminal code is blue. This state persists until the console window is closed.This does not happen when the CentOS machine is used directly, e.g. via a Hyper-V connection window. Unsure if this occurs with other OS versions/distros, other
vi
versions, or other "flavors" ofvi
such asvim
.I am aware that the wiki explains the caveat that the client has outstanding issues with interactive applications such as
vi
, but I figured it couldn't hurt to point one specific one out that I didn't see an issue for before.Expected output
Console to retain its default text color after
vi
is launched on the remote CentOS machine.Actual output
The text was updated successfully, but these errors were encountered: