Open rgbkrk opened 9 years ago
I think rack init
should take care of everything for you and users who want a custom setup can follow the instructions in the docs to set it up.
How would this work on windows?
It currently dumps out Command completion not available for Windows
.
I think rack init should take care of everything for you and users who want a custom setup can follow the instructions in the docs to set it up.
The problem isn't that I don't want to make it easy, the problem is that when/where things get sourced is inconsistent.
At a terminal on OS X, run a new bash shell
$ bash
$
Then try to autocomplete on rack
. It won't work.
Why is this important? Well, for things like kitematic, various editors, etc. they'll drop you into a new bash shell with what comes from ~/.bashrc
but not ~/.bash_profile
. This is why people end up making their ~/.bash_profile
consist solely of:
source $HOME/.bashrc
On a new Mac, this confuses the hell out of people for why sometimes things get sourced and sometimes they don't.
"Would you like to insert this into your .bashrc, so it will be available in the terminal from now on? [Y/n]"
Give them the option, default to Y. Informs, saves user trouble, puts it in best place.
I like the Y/n option.
:+1:
I'm not convinced there is anything to do here that makes it trivial to solve all cases. I'm going to move this to post-public-beta unless there is a compelling argument against.
:+1: to this. I like bash init generating the files, I don't like it modifying my .bashrc.
If it's going to put stuff in places it should put them in the right place: /etc/bash_completion.d/
as rack
for completions and /usr/share/man/man1/
for rack.1
Otherwise provide instructions and let me do it myself.
I like the interactive thing.
Rather than knowing/understanding where people want to put the
source
ing (OS X assuming mostly~/.bash_profile
with some caveats), haverack init
spit back what to source:Thoughts?