Vim run commands from bash script and exit without leaving shell in a bad state

Question

If I do:

echo 'vim +BundleInstall +qall' | bash

it installs my bundles correctly, but leaves the shell in a bad state (ncurses options) because of the pipe.

Is there a way to prevent the shell from being in a bad state?

Same for the minimal test case: echo 'vim +qall' | bash

Similar to: Run vim command from commandline, but the question there was for an interactive shell, so vim +BundleInstall +qall was fine.

I want to do this to be able to automate Vim plugin installation as:

wget -O- http://a.com/bootstrap-scrit.sh | bash

in a bootstrap script that currently contains vim +BundleInstall +qall. This command can be changed if needed.

@devnull I can, but I would rather do everything automatically, so I can leave my bootstrap script running, come back later when its finished, and start working immediately. Cloning take 5 minutes. — Ciro Santilli OurBigBook.com, Apr 27 '14 at 11:25

score 2 · Accepted Answer · answered Apr 27 '14 at 12:48

2

You can source your script instead, like so:

. <(wget -O- http://a.com/bootstrap-scrit.sh)

answered Apr 27 '14 at 12:48

gniourf_gniourf

This one made me smile. The only downside is that stuff like variables defined locally in the script will "spill over" to the main shell, but true, this is not very likely to be a problem for a bootstrap script. – Ciro Santilli OurBigBook.com Apr 27 '14 at 12:53
@CiroSantilli I was assuming that your script doesn't do anything evil. Hey, it's just a bootstrap script, right? if you really need to define variables and do evil stuff inside your script, you can always enclose the bad parts into parentheses `(...)` so that these parts are executed inside a subshell and won't alter the main shell. – gniourf_gniourf Apr 27 '14 at 12:57

1 Answers1