4 ms·
And you can't remap things in Vim because ... ?
by pritambaral 10y ago
And you can't remap things in Vim because ... ?
- maratc 10y agoWell, I can remap things, but then it wouldn't work on a remote aws machine, or at my colleague's machine, etc. And this is not only Vim. Having a system-wide set of shortcuts without having to fight the system is extremely powerful. I have suggested Win-C/Win-V to the elementaryOS guys -- as an addition, not a replacement -- but they weren't interested.
- pritambaral 10y ago> Well, I can remap things, but then it wouldn't work on a remote aws machine, or at my colleague's machine, etc. And this is not only Vim. Hmm, backtracking to my grandparent comment, if you can map the terminal emulator to do the equivalent of C-c upon C-S-c, then why not do the same with C-v and C-S-v. Just send the ASCII keysequence for C-v down the shell. ---- > Having a system-wide set of shortcuts without having to fight the system is extremely powerful. This follows the exact same argument OS X has to not using Ctrl-c, Ctrl-x, and Ctrl-v for copy, cut, and paste: history. When I first used OS X, coming from a Windows and GUI Linux keyboard usage background, I found that odd similarly to how OS X terminal users find Linux's terminal shortcuts. But hey, historical decisions have stuck. And it's not that hard to commit to muscle memory a few platform differences here and there. There certainly are many OSX-isms a not-primarily-OSX user has to deal with.
- maratc 10y ago> if you can map the terminal emulator But then I would have to press some keystroke to copy/paste in terminal, and some other keystroke everywhere else. This is the default state of things in Linux today. This means my muscle memory needs to be contextually aware; today it's not.