-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Support missing keybindings in PowerShell #45705
Comments
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. |
@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). |
@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. |
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 |
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. |
@DarthSpock I'll be working on that soon 😃 |
Don't suppose it would be too much to ask if we get ColorTool support in VSCode is it? 😉 |
@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 |
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. |
@DarthSpock I'd rather not add something like that to core, sounds like a good idea for an extension though to convert |
I guess the idea of an extension would work. Considering the support comes from MS, I would request that this would be an offical extension from MS to ensure there aren't any loose bugs and would maintain the proper support as ColorTool adapts. Is there a repo for that type of request or is this one good enough? |
@DarthSpock well I know that the VS Code team won't have any time to work on that as it affects such a small portion of the users:
This probably is the right repo for such a request but we need to close issues like this in order to keep the issues manageable. This is a good candidate for a community extension. |
Sounds fair. |
Hi @Tyriar, is there any update regarding this issue (typically ctrl+backspace to delete a word)? or any extension that would fix it? |
@f-roche you could try using |
Some of this works now with the emacs edit mode, you can also configure your own keybindings. Going to close this issue off as it's pretty general, please open focused issues if you cannot configure your own PSReadLine options for this. Note that you can enable escape sequence logging in Insiders which can tell you what character codes are sent when you type: https://github.com/microsoft/vscode/wiki/Terminal-Issues#enabling-escape-sequence-logging |
This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider. If you wonder what we are up to, please see our roadmap and issue reporting guidelines. Thanks for your understanding and happy coding! |
Looks like this will now be possible to do when shell integration is enabled using this technique 🎉. Ctrl+space on macOS/pwsh 7: |
Default keybindings on macOS:
|
Windows default keybindings:
|
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:
All platforms:
Perhaps some API like this would be able to handle the selection requests:
/cc @sbatten
The text was updated successfully, but these errors were encountered: