Not to rain on anybody's parade here, but for first-time vim users I recommend not using any plugins and only selectively adding them one at a time after the basics (buffers, navigation, some ex mode, etc) are at least somewhat familiar. Getting started with plugins enabled makes it hard to understand where vim stops and plugins begin and make switching to a different (someone else's) vim setup confusing at best. It…
Square open-sources its Vim repo, Maximum Awesome
71–80 of 145 posts
Re: Square open-sources its Vim repo, Maximum Awesome
#72I would love to know why they have chosen Pathogen instead of Vundle to manage plugins. As hard as I try, I can't see any reasons why Pathogen is greater than Vundle. Can someone enlighten me?
Chalk it up to different preferences. I prefer Vundle too, never could get Pathogen to work, but Vundle just does for me. But others were using Pathogen before Vundle appeared and have no reason to switch.
Re: Square open-sources its Vim repo, Maximum Awesome
#73Great to see some love for tmux. Terminal vim + tmux is a lot more powerful than Gvim or MacVim. That said, I started using vim with Janus and while it convinced me that vim could be a great modern editor, it left me too confused when I tried to make my own customizations. I ended up ditching it and hand-picking my own plugins. I suspect a completely new vim user would likely experience the same process with Maximum…
gitgutter, ctrlp, and pretty much anything from tpope are all great in this regard: they do one localized thing and it Just Works. (Downside is when that "one thing" is a shortcut or function, and with no other cues I forget I even have the plugin installed.) On the other hand I've had pretty terrible experiences with SuperTab, which required a lot of fiddling and still breaks my Tab key sometimes, and ctags is such a pain that I've never gotten around to making it actually work. But those are useful enough that they end up in most plugin bundles, so you get a Cartesian product of the interference and brokenness of all of them.
Re: Square open-sources its Vim repo, Maximum Awesome
#74Ok, got this cloned and installed. If I'm moving from Sublime to vim, where do I go now? I know a few basic vim commands (switch modes, edit, write, quit) but have never used it to work on a complete project in a directory.
Re: Square open-sources its Vim repo, Maximum Awesome
#75Not to rain on anybody's parade here, but for first-time vim users I recommend not using any plugins and only selectively adding them one at a time after the basics (buffers, navigation, some ex mode, etc) are at least somewhat familiar. Getting started with plugins enabled makes it hard to understand where vim stops and plugins begin and make switching to a different (someone else's) vim setup confusing at best. It…
Re: Square open-sources its Vim repo, Maximum Awesome
#76Am I missing something? What makes this "maximum-awesome"? This is your average vimrc with the regular plugins you seen in every vimrc over at GitHub.
Because it's Square and they're hip. Whenever they open the lids of their macbooks its you know... just awesome. Not to mention it's not maximum awesome: CtrlP > Command-T and Vundle > Pathogen.
I disagree on that front. Managing git repos is easier for me to do the way I always do it than with a slightly auto-magic system specific to those sort of git repos. Pathogen does a little, but does it flawlessly. Vundle does more, but the more it does is far less elegant.
Re: Square open-sources its Vim repo, Maximum Awesome
#77Do lots of people use let mapleader = ',' instead of Ctrl? Also does anyone see where they are setting the /// to comment? Commentary uses gcc and I don't see it in their vimrc.
Re: Square open-sources its Vim repo, Maximum Awesome
#78Am I missing something? What makes this "maximum-awesome"? This is your average vimrc with the regular plugins you seen in every vimrc over at GitHub.
Re: Square open-sources its Vim repo, Maximum Awesome
#79Do lots of people use let mapleader = ',' instead of Ctrl? Also does anyone see where they are setting the /// to comment? Commentary uses gcc and I don't see it in their vimrc.
I went crazy, and it's a bit more tricky to pull off, but `q` is my leader key. Haven't looked back. P.S. I mapped `Q` to recording Macros, since the default use of `Q` is completely useless to me.
Re: Square open-sources its Vim repo, Maximum Awesome
#80Great to see some love for tmux. Terminal vim + tmux is a lot more powerful than Gvim or MacVim. That said, I started using vim with Janus and while it convinced me that vim could be a great modern editor, it left me too confused when I tried to make my own customizations. I ended up ditching it and hand-picking my own plugins. I suspect a completely new vim user would likely experience the same process with Maximum…
The only thing I really like about MacVim as opposed to Terminal vim + tmux is how fast the cursor moves can move around.