121–130 of 145 posts
Surprised that people are actually trying this. IMO there are far better configurations out there if you want to try a pre-tailored one. Google for them, i'll add my personal favorite here since people are actually up-voting and installing this less than impressive config. If you use ruby/rails try yadr https://github.com/skwp/dotfiles . If you don't use ruby, it (imo) still has one of the best key maps/configs for b…
Great 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…
Oh God, here we go...
Earlier quoted context omitted.
Completely respect where you're coming from, but totally disagree. I made a few abortive switches to Vim that didn't last a week because my productivity was too hampered and the environment too extreme & foreign. To a newcomer like me, Vim's built-in help was less than worthless, since you pretty much need to know the Vim term for what you're looking up to find it. Googling around wasn't much more effective (there's…
The problem wasn't the "extreme & foreign environment", the problem was that you thought wrongly that you could learn Vim as if it were a regular editor. Learning Vim is a side project: something you do casually, slowly, until and if you are able to do the actual switch. Those braindead distributions are just smoke mirrors for lazy and pressed people: they provide training wheels but they actively prevent you from ac…
Great 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…
It's not like tmux didn't get any love these days.
I 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.
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…
Basically it follows the KISS, and in some sense UNIX, principles.
I have never used the vim distros but I have gotten to a point where I just rm -rf'd my whole .vim dir and started over with only the plugins I required at the time. Then added more as I needed them.
Of course, I have always managed well without the file browsers many use.
Earlier quoted context omitted.
> I made a few abortive switches to Vim that didn't last a week because my productivity was too hampered and the environment too extreme & foreign. That was my experience as well. I was pretty comfortable using vim in emergencies but the few times I tried to make it my full-time IDE failed very quickly. Once I stole Gary Bernhardt's dotfiles[1] I was able to stick with it because I didn't have to start from scratch w…
Vim can't be an IDE (it lacks the most important aspects of an IDE), no wonder your attempts failed.
Earlier quoted context omitted.
Vim can't be an IDE (it lacks the most important aspects of an IDE), no wonder your attempts failed.
what exactly, in your opinion, are the most important parts of an IDE that vim lacks?
* The ability to run this engine in the background.
* A unified API that would make possible for plugin authors to interact seamlessly with that engine but also between each other.
* Certainly a thousand of minor details.
You can add as many fancy plugins as you want, you'll never get an IDE.
You'll get something that looks more or less like an IDE and works more or less like an IDE, but not an IDE because an IDE is not a text editor with a file explorer on the left, a class explorer on the right and a list of compile errors underneath. It is much more than that and Vim doesn't have and can't have that "much more".
Unless you count external compilers/debuggers/profiler/linters as that "much more" but that's still not an IDE. A DE, maybe, but certainly not "I"ntegrated. Well, not even an "E"nvironment, actually, given Vim's design principles.
Am 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 also worked with the author of CommandT at that job, which was nice.