Ctrl+V (vertical selection in Vim) does not work

[vadimkantorov]

I guess it's because it's now bound by default to do paste.

I think it's quite a pain point for anyone new to Linux development on Window: vim basic functionality does not work :(

[vadimkantorov]

I think MS Terminal should allow some Keybinding Profiles (like Visual Studio / ReSharper do) and hopefully it would be super-easy to change them. It may seem that satisfy everyone is impossible :(

[zadjii-msft]

So we've probably had this discussion 1000 times across this repo now. The basic conclusion is always the same:

It may seem that satisfy everyone is impossible

When we only had Ctrl+Shift+C/Ctrl+Shift+V as the copy/paste keybindings, users were unhappy. Now that we've added back Ctrl+C/Ctrl+V, users are still unhappy.

With the new "default" settings in 0.11, the balance we've tried to compromise on is the following:

• Ctrl+Shift+C/Ctrl+Shift+V are bound in defaults.json, and users will need to actually unbind those keys to disable their functionality.
  • These are the keybindings we've always had for copy-paste, so breaking them seemed like a terrible idea
  • Nobody was really complaining about these being used for copy/paste as opposed to something else
• Ctrl+C/Ctrl+V are now listed in new user's settings.json file when they create a new settings file.
  • If they don't like them, it's trivial to just delete them from the file.
  • Ctrl+Shift+C/Ctrl+Shift+V will still work if the user deletes the Ctrl+C/Ctrl+V bindings from their settings.json

[vadimkantorov]

I understand there're tradeoffs. I understand one can fix manually the keybindings by editing settings.json. I understand this was discussed many times before.

The point of this issue is to point out a concrete example of very common, wide-spread vim functionality that breaks. This is not just "I don't like Ctrl+V", it is a problem that almost every vim-user will encounter. Since it's wide-spread, I think, it calls for more special consideration: e.g. big letters in README about this specifically or MessageBox on first launch, or an explicit invitation to change keybindings on the first launch, or sth else.

The profile idea would allow users to change multiple keybindings at once without encountering the problems and fixing them one by one. The same motivation applies to Microsoft Visual Studio / IntelliJ etc. If my preset is e.g. "Gnome Terminal", I'm sure everything will "just work" and have correct expectations about the chosen tradeoffs.

This is somewhat related: #5638

[FossPrime]

I'm actually having issues with ctrl+shift+v behaving erratically. It's not pasting new lines apparently. Right click doesn't work. Scroll doesn't work.

Can you please for once just allow us to select a default that makes this work like iterm, Terminator, Termux, Gnome Terminal and Mac's terminals. It's all we ask.

[DHowett-MSFT]

So, this would ultimately be solved by /dup #5790, which I've promoted to be "profile-specific keybindings". FWIW: I don't like binding ^V by default either, but I more don't like how literally 50% of all our users yell at us regardless of the choice we made. 😄

All we can do is add more flexibility.

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!