![]() My tips for anyone learning to use vim for everyday development would be some common tab commands: :tabnew to open a file in a new tab, :tab sball to show all currently open buffers in separate tabs, gt and gT to jump to the next/previous tabs. Yeah, I initially learned vim because I didn't really have a choice (it was expected for the class that we would use vim), and I remember it being very painful in the beginning. However, just like any other tool you use on a regular basis, those commands become muscle memory very quickly and you don't even think about it. Now I use vim for work, mostly editing c code. I have a very barebones vimrc and have never installed a little bundle or package. I use it mainly because of its simplicity and terminal integration. ![]() I can't say I'm a very visual person though. I get distracted with too many bells and whistles and often times even just switching windows causes me to get distracted by the interwebz (.i'm a bit add), so I like the simplicity of a blank screen. (Small confession: I also really feel kind of bada$$ when I'm sitting behind a black terminal with green text.) Point being, vim isn't for everyone, but using vim doesn't have to be this big giant complicated endeavor that everyone seems to make it out to be. > I just can't be bothered with fiddling with config files and installing little bundles and packages for every functionality. This is exactly the reason I decided to make what is probably a lifetime choice to use vim going forward. The vim defaults are ideal for general purpose editing. It's true an IDE or the right modern editor might have things set up with nice defaults for x or y language, but pick five editing tasks at random and you'd be hard-pressed to find a better editor out of the box than vim.īeing able to competently edit any file out of the box on any system affords me a great mental flexibility. It lowers the barrier for learning new languages, or even switching platforms (I like OS X now, but I don't want to be locked in forever when Apple dials up the consumerification to 12). The main disadvantage is that vim really can't compete with IDEs for boilerplate-heavy verbose languages like Java, but I'm not particularly interested in learning languages like that. ![]() Now it's true that I will tweak my config and go and seek out some plugins to enhance my core workflows slowly over time, but that's just the icing on the cake. Mainly I focus on mastering core vim and I do with reasonable confidence that the investment I'm making now will pay dividends 10, 20 and 30 years from now. > On top of that the whole "language of editing" and combining noun,verb,adjective commands, etc. #Macvim green extra characters windows#ĭoesn't really appeal to me because I'm too visual when I'm editing code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |