34 ms·
I realize this is a different project, but since it looks similar: installing Janus was the worst decision I ever made while looking to improve my Vim experienc
by exogen 14y ago
I realize this is a different project, but since it looks similar: installing Janus was the worst decision I ever made while looking to improve my Vim experience.
It actually made Vim worse, sometimes by just slowing things down, other times because of the lack of quality control in the bundled plugins. One plugin actually caused data loss many times – it completely froze the editor when a certain syntax pattern was typed. All with just the default Janus settings.
To that effect, I hope quality control in spf13 is really, really good.
- olalonde 14y agoI think you are an exception. I can't get anything done with vanilla Vim (no smart indentation for instance) and install Janus anytime I need to use Vim on a new shell.
- sigzero 14y agoA couple of lines in your .vimrc and boom you have that and more.
- deleted 14y ago[deleted]
- olalonde 14y ago... or one bash command to install Janus.
- alexkus 14y agoI've used vi/vim for ~20 years (I have memories of using it in '92 when I had an Amiga B2000) and I've never installed a single extension/package/what-not. The corporate development environment I'm in means it's a huge amount of work to get anything installed on a wide range of platforms (6 different OSes not including Windows) and on a large number of machines. For various security reasons, my home directory is not shared amongst all of the machines, which could have made it easier. However, the main reason is that I often go to customers to solve problems and I have to use what they have installed. I can't go asking someone to install vim and a bunch of extensions on their production servers just to make me feel comfy; I have to rely on the lowest common denominator set of basic tools that are usually installed; vi (even ed), sed, awk, sh (can't even rely on bash being installed). Don't get me wrong, I've nothing against people using vim with a whole bunch of extensions, it's just not for me. But not being proficient in the basics can be a bad thing, especially when it's usually a tricky/pressured situation where you're left without your favourite dev environment.
- spf13 14y agoThis is my project. I was surprised to see it on HN today. It has a lot in common with Janus on the surface. IMO Janus is also a good project. Where it differs is spf13-vim is focused on cross platform dependency, keeping with vanilla vim feel and having no external dependencies (with the exception of git). My understanding on Janus is that it focuses on Ruby (spf13-vim supports Ruby well, but Python, JavaScript, PHP, Shell, Scala and a bunch more as well). Janus includes many plugins that depend on Vim Ruby support and is definitely focused on the MacVim platform. My goal was a Vim configuration you could run anywhere whether Linux, Mac or Windows to efficiently develop in any language. Hopefully you will find the quality control is good, general feedback is very positive. If you find issues please submit a issue on github or even better a pull request. You can see that I'm very responsive to pull requests.
- vessenes 14y agoThanks for spf13 -- I use it every day, on Mac and Linux, with Python. I do have one persistent, annoying problem with it, though, since I've got you here -- inserting close braces/parens OFTEN doesn't work with whatever plugin you use for the auto-closing. How do I turn it off? I remember trying to get rid of it, and failing miserably.
- arkenflame 14y agoI also use this daily, and have the same problem. I suppose this speaks to the weakness others have expressed (in using a premade configuration setup vs. slowly rolling your own), but I have otherwise found spf13-vim very useful.
- FuzzyDunlop 14y agoI agree with the sentiment, and it's exactly why I switched from a ready made emacs setup to a custom-rolled config. Most of the stuff bundled in it isn't really necessary, and just makes it harder to understand the clean environment if you're new to it. Even though it's more work, it's nice to know exactly how you're configuring your own environment, and you get to learn more about it as you do configure it. To that extent I'm not even a fan of emacs' new package manager.