From 99c45dd5d5c3efb53fb97d41bbec7713a74cb1ff Mon Sep 17 00:00:00 2001 From: bagajjal Date: Mon, 13 Mar 2017 19:07:16 -0700 Subject: [PATCH] Updated Terminal Info (markdown) --- Terminal-Info.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Terminal-Info.md b/Terminal-Info.md index f8fc6e9..f2ecee2 100644 --- a/Terminal-Info.md +++ b/Terminal-Info.md @@ -11,7 +11,7 @@ For more information, please go through https://msdn.microsoft.com/en-us/library If you are using the openssh client, a) Using windows 10+ OS then windows console (cmd.exe/powershell) has the support to interpret the VT sequences received from the SSH server. We simply pass the raw VT sequences to the console (cmd.exe/powershell). If you are facing any issues then it should be fixed by the windows console team. - If you want to use the inbuilt VT100 ANSI parser (which is 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 to 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.