3 ms·
> I've been using it full-time for just over three months now. That's it: you just need to give it more time. One simply can't expect to fully climb vim's lea
by bpizzi 13y ago
> I've been using it full-time for just over three months now.
That's it: you just need to give it more time.
One simply can't expect to fully climb vim's learning curve in just a quarter of a year.
Your brain can't adapt so rapidly to so much new shortcuts.
> Jump to CSS selector. Jump to class. Fuzzy string matching. All these things and more are what I am used to. Vim just can't do them.
That's one example among others: there's vim's marking system for that, and your brain isn't just used to it now.
You find it slow, broken and not user-friendly, but it's not really, it's just that you need to give it time to master it.
My 2c advice: it you really want to like it, keep going and give it a full year.
If you think you can't give it more time, then Vim isn't for you and some commercial editors might do it.
I've been there, I know your current feeling. I'm a happy vimmer now but it hasn't been the case for something like a year.
There's a reward for real vimmers: you'll never need to switch anymore to another editor, because Vim is there, powerfull, opensource, free, multi-plateform, and you know how to use it smoothly.
- pestaa 13y agoI like the spirit, but how will Vim's marking system help me jump to a CSS selector in an unbuffered stylesheet? I'm really curious; missing this feature from heavyweight IDEs.
- bpizzi 13y agoBeen there also. _My_ solution was not to rely anymore on stuff provided by a heavyweight IDE. "Jumping to somewhere in an unbuffered file according to where I am in the current buffer", that is actually depending on a background worker that knows a very specific set of rules and use it to constantly cycle threw the filesystem. Which bg process is usually provided by tanks like Eclipse. With the time I've found something that matches that behavior without the payload on the computer, and guess what, it's my brain. I'm no more in pain of jumping to the definition of a css rule, because I know which css file I have to invoke and I can do it _very_ quickly thanks to Control+P, and jumping to the definition is a matter of one or two "/". Of course you need to organize things smartly in your project if you ever want to do that without too much thinking time, but hell, I count that on the bright side of this solution.