51–60 of 117 posts
set relativenumber I had been using Vim for years, and this is fundamentally one of the most useful settings I came across. I think it's only available it the latest rel. Funny side note, I was out on the town one night and saw a bunch of guys and girls hacking on their laptops... in a club. I noticed one guy using Vim, came up behind him and told him he has a good taste in editors. It turns out he's Jay Freeman (sau…
set relativenumber I had been using Vim for years, and this is fundamentally one of the most useful settings I came across. I think it's only available it the latest rel. Funny side note, I was out on the town one night and saw a bunch of guys and girls hacking on their laptops... in a club. I noticed one guy using Vim, came up behind him and told him he has a good taste in editors. It turns out he's Jay Freeman (sau…
Still can't decide if Vim is actually worth all this trouble, or if it's a cult.
I've used Pathogen previously and I have to say I much prefer Vundle. It's the only plugin I have to manage in my .vim directory. All the plugins I use are listed right in my vimrc, and running :BundleInstall does a git pull from each plugin's repository which gives me the latest updates. I use terminal-based vim for all of my coding and text editing all day, and my vimrc is only 91 sloc. https://github.com/tomhsx/do…
Nicely done. A new or returning vimmer will profit from following his advice. His best recommendation is at the top: don't configure a lot of settings and plugins at first. Start with a minimal setup, and slowly work up from there when needed . In particular, don't copy someone's huge .vimrc. In fact, that's good advice for any tool or technology: start minimal, and only add what you need, when you know you need it.…
It's also true that Vim 'suffers' from the open source infinite configurability issue. That is, it is so configurable that you'll spend a significant amount of time configuring it to your tastes rather than getting work done. This tails off over time of course. Slightly more awkward is that it's also easy to shoot yourself in the foot. For example my current config has an issue where on rare occasions undo sporadically fails, and ends up undoing line insertions by deleting the wrong line! Ouch. I still have several such issues, but not enough to deter me as yet.
Another thing to consider is that Vim is not equally suited to all developers. If you're editing a bunch of different file types with mostly consistent libraries I think it's a great fit, which describes a lot of web developers. In that case you just want world class text editing. If you're editing mostly C++ with a bunch of different APIs and libraries, the loss of decent codesense/autocomplete forces you into lots of very slow doxygen searching in a browser. I've tried various solutions to this such as clang complete and eclim, but ultimately Vim is not an IDE and there's no way to make it act as one.
Overall I'm happy to have made the switch though, since the editing itself is so very smooth. It's great to have the same environment in a remote shell as well.
Having unrelatedly just started using CommandT today, let me say how amazing it is. I've been using vim as a supreme novice for a few years, and have only really tried to get to know it better in the past six months after switching to OS X and getting to use MacVim. And already in one night CommandT has blown me away with how timesaving it is, and how much time I've wasted in the past not using it.
I'm happy to have finally gotten comfortable with enough of the movement/editing commands to use them every day for real work. However, I just use Vintage mode in Sublime Text 2 because I like having nice file browsing/tabs and other niceties of Sublime Text 2. Am I missing out on much by not using straight vim?
I loved Sublime Text 1, and I really love Sublime Text 2. With the addition of Vintage, Sublime Text is slowly becoming the ultimate answer to the question of which editor to choose.
But Vintage mode is really buggy, and misses a lot of very important features that vim has. There is work being done on it, and it is getting better, but vintage mode does not come close yet to the power of vim. And there are a few bugs that make it hard to get used to some of vim's more powerful features.