3 ms·
Because i can install vundle with a single line in my setup script (already have a "provisioning" kinda script for each time i fire off a machine). I dont have
by jmcdiesel 10y ago
Because i can install vundle with a single line in my setup script (already have a "provisioning" kinda script for each time i fire off a machine).
I dont have to update that script for new plugins, its a single "Vundle user/repo" in the vundle.rc file. Vundle then installs it, and handles it.
Could it be scripted, sure... but its much more readable in the vundle form (or other managers for vim), and its also in a more logical place... and its portable, even to a windows machine... its kinda a separation of concerns kinda thing...
- hellcow 10y ago> I dont have to update that script for new plugins, its a single "Vundle user/repo" in the vundle.rc file. You either add a single line to your vundle.rc file, or you add a single line to your bash script.
- jmcdiesel 10y agoStill doesn't address separation of concerns... if you prefer a single monolithic script to do everything, thats cool, im not trying to change your mind, but for my tastes, i want my provisioning script to be as simple as possible, concerning only what it needs to, and let the apps configure themselves in a way that is obvious to anyone who uses my scripts (a few of my fellow devs use my stuff to bootstrap their setup)