The trouble here is that even though the productivity will eventually increase, the learning curve will take too much of a tool. Yet I'm determined to give vim a solid chance soon once my current projects are over.
The trouble here is that even though the productivity will eventually increase, the learning curve will take too much of a tool. Yet I'm determined to give vim a solid chance soon once my current projects are over.
This is how I use vim. It’s great for quick edits and ssh boxes but I’m not a fan of maintaining all the plugins and settings manually so I have a barebones vim setup.
I don't need to turn vim into an IDE, and nor do I want to. However VIM is an amazing tool that's worth learning on its own merit. It's the text editor that's everywhere you need it to be, and I have never had an admin say "NO" to adding it into a box or environment to work/test.
You can get around with relatively little know-how. The problem is that knowing what you need to know is not easy.
Most tutorials, including the official one, focus too much on details and too little on concepts to get you bootstrapped.