4 ms·
It isn’t silly nor did it require you to jump to the defense of vim’s behavior. It was a simple statement that vim’s functionality can be clunky and with all o
by garciasn 5y ago
It isn’t silly nor did it require you to jump to the defense of vim’s behavior.
It was a simple statement that vim’s functionality can be clunky and with all of its flexibility, it cannot handle something as simple as nano/pico’s method for keyboard copy/paste.
It’s literally the one functionality I would love to become available in vim that exists in nano/pico which would make mine (and likely many others’) lives and efficiency better.
- maddyboo 5y agoBut it can handle it with a very small bit of configuration, as I’ve shown above. I am not trying to defend vim here, the editor you use or prefer has no effect on me. I’m just trying to point out that if you want it to work in a certain way, it’s almost always possible.