Those of us who preferred the "Linux" terminal behavior to pass Ctrl+ V to the shell so that WSL distributions would handle it as we were used to.Side note: As you can read in this Github issue, the Windows Terminal team was torn between two groups here: If not, feel free to Add a new action and set it to one or the other, or whatever you want. I believe that Paste should still be bound to either Ctrl+ Shift+ V, Shift+ Insert, or both. Scroll down to the Paste action which is bound to Ctrl+ V.If you are in a recent release of Windows Terminal:
Simply unbinding the key should allow the shell to handle its default behavior (the "verbatim insert" operation that will allow you to insert a Tab character). That said, the problem should be that the default keybindings in your installation have Ctrl+ V set to the Paste operation, as you've found. I did attempt to bring up a VM where I have Windows Terminal installed (post-change), but I hadn't used it in a while and it's not quite functional at the moment. And I don't plan on uninstalling/reinstalling because I prefer the old behavior. So unless I uninstall/reinstall, I'm not going to be able to exactly reproduce what you are seeing. The WSL team changed the way that Ctrl+ V operates in Windows Terminal in April 2020, but only for new installs. Apologies, but I'm going to have to go from memory/theory on this a bit.
0 kommentar(er)
