Ctrl + h's behavior is differ from command prompt window

[koron]

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.592]
Windows Terminal version (if applicable): 0.8.10261.0

Any other software? no

Steps to reproduce

just type Ctrl + h

Expected behavior

Delete a character before the cursor, as same as command prompt window.

Actual behavior

Delete a whole word before the cursor.

Notes

I guess that this is a side effect of #3935

[koron]

it affects vim in cmd in WindowsTerminal.

when i hit Ctrl+h in insert mode, i got Îz.

I expected to delete a character before the cursor.

[DHowett-MSFT]

So, this is one of those issues we might just have to live with for now. ^H means, to many other applications, the same thing as Ctrl+Backspace. To the rest of them, it means Backspace. It looks like Vim for Windows has an explicit binding for <C-H>, but now it's receiving <C-Bksp>. In Vim for LInux this works fine.

We may need to wait for /dup #879 so that Windows Vim can use raw key mode.

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

[moetayuko]

@DHowett-MSFT I encountered the same issue, but don't think it's related to Vim for Windows.

Here's my result:

Setup	Result
WT (wsl) + Vim	Y
WT (wsl) + Vim over OpenSSH_8.1p1	Y
WT (powershell) + Vim over OpenSSH_for_Windows_7.7p1	N
WT (cmd) + Vim over OpenSSH_for_Windows_7.7p1	N
powershell.exe + Vim over OpenSSH_for_Windows_7.7p1	Y

[DHowett-MSFT]

This is one of those weird things 😄 WT and OpenSSH_for_Windows actually use the same translation backend to talk to windows console applications, but WT uses a newer version of it. The older version was more compatible with certain windows apps, but it worked less well with everything else.

[koron]

this problem is introduced by #3935 .
#3935 solved only one problem which describled in #879 in wrong way.
so i think that #3935 should be reverted.

[DHowett-MSFT]

The problem is that 3935 solved the problem described in 879 the only way that is correct for a Terminal emulator. We're right here on the boundary between what consoles and terminals need to support, and we made the call to be a terminal first.

I'm not certain that was the right decision?

[debuuu]

The bot mentioned a "referenced thread", where is that? Would like to track this, it broke some Vim muscle memory for me.

[DHowett-MSFT]

Sorry @debuuu - it's referring to #879

[koron]

the problem is that the terminal generate same codes 0x08 for ctrl+h and ctrl+backspace.
but #3935 resolved it by parsing the code (0x08) as ctrl+backspace always.

i don't think this is correct way to fix.

[wmertens]

I'm probably re-hashing old conversations, sorry, it's hard to read all threads on GitHub.

How about sending esc+ctrl-h? That seems to always work in the shells I came across?