tyler.durden/Win32-OpenSSH
1
0
Fork 0
mirror of https://github.com/PowerShell/Win32-OpenSSH.git synced 2025-07-27 07:54:50 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated Terminal Info (markdown)

bagajjal 2017-03-13 19:10:01 -07:00
parent b949462df8
commit fc6255c122
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Terminal-Info.md

@ -13,13 +13,13 @@ If you are using the openssh client,
If you want to use the inbuilt VT100 ANSI parser (that's part of the openssh client) then set the environment variable "SSH_TERM_CONHOST_PARSER" to 0. If you want to use the inbuilt VT100 ANSI parser (that's part of the openssh client) then set the environment variable "SSH_TERM_CONHOST_PARSER" to 0.
b) Using prior versions of windows 10 OS then the raw VT sequences will be parsed by the inbuilt VT100 ANSI parser as part of the openssh client. We have fixed most of the issues and have no plans to extend to VT100+ sequences. b) Using prior versions of windows 10 OS, the raw VT sequences will be parsed by the inbuilt VT100 ANSI parser that's part of the openssh client. We have fixed most of the issues and have no plans to extend to VT100+ sequences.
If you want support for the VT100+ sequences then please upgrade to windows 10+ OS or use the third party tools like putty, Cygwin, etc. If you want support for the VT100+ sequences then please upgrade to windows 10+ OS or use the third party tools like putty, Cygwin, etc.
**For UNIX users** **For UNIX users**
If you want to use vi / top / man, etc commands while connecting from windows client to Linux server then please follow these steps If you want to use vi / top / man, etc commands while connecting from windows client to Linux server then please follow these steps
1) Upgrade to windows 10+ OS. 1) Upgrade to windows 10+ OS.
2) Set the non-legacy console mode in the console properties, 2) Set the non-legacy console mode in the console properties,