Support missing keybindings in PowerShell

[Tyriar]

Currently various features don't (typically?) work in the prompt on Windows, for example ctrl+backspace to delete a word, ctrl+shift+left to select the word to the left of the prompt etc. We could expose some API in xterm.js to be able to handle this. For example:

Windows:

• backspace, delete: Press backspace/delete the number of characters that are selected
• ctrl+backspace: Backspace the number of chars in the preceeding word

All platforms:

• ctrl+shift+left/right, shift+left/right: Select from the cursor

---

Perhaps some API like this would be able to handle the selection requests:

// Select from cursor, in the future if we wanted to select from some other origin we
// could add a third parameter
select(direction: 'left' | 'right' | 'up' | 'down', amount: 'word' | 'char'): void;

/cc @sbatten

[sbatten]

note that there are also differences based on shell in Windows as well. e.g. ctrl+backspace and shift+left do not work as expected on WSL.

[Tyriar]

@sbatten not so sure we should do much for different shells, we'd probably need a when clause or something to do it right (which is getting quite complicated).

[sbatten]

@Tyriar Fair and agreed. I just want to make sure the changes don't break any experiences in WSL by adding keyboard functionality that didn't exist previously as WSL is something users will expect to work.

[1800Zeta]

Upvoting this, I'd like to see the ability to control backspace and delete a word in the terminal on Windows 10 please. Thank you

[WSLUser]

Is it possible you guys can take advantage of the work the Console team has done via their APIs? You guys are ahead in a few ways than the Console but having features of the Console lacking in the VSCode terminal would be great. Also, for shells, I think you guys have to account for Sets plus whatever shells might be generated from the new APIs being developed by the Console team to allow various terminals to be ported to Windows that are currently only existing in Linux.

[Tyriar]

@DarthSpock I'll be working on that soon 😃

[WSLUser]

Don't suppose it would be too much to ask if we get ColorTool support in VSCode is it? 😉

[Tyriar]

@DarthSpock I don't think we'll support cmd.exe ColorTool, but themes can set this and you can override the colors like this: https://github.com/Tyriar/vscode-snazzy/blob/b155eb74098971c3daca73942d7d626c8bcc2ec9/snazzy.json#L2-L22

[WSLUser]

I think the big thing is being able to read the Themes directory. I wouldn't care so much about having the command controls from ColorTool. I just would like the terminal to accept the Iterm2 schemes (in addition to whatever other themes you want). How that happens is up for interpretation. I can see myself sticking purely to the VS Code terminal without ever touching a real console if we had that type of support.

[Tyriar]

@DarthSpock I'd rather not add something like that to core, sounds like a good idea for an extension though to convert .itermcolors files into VS Code settings.