moving specific things away .bash_profile

[noqqe]

Hi,

since i use bash-it i wonder why all these specific things are placed in bash_profile
i'm talking about:

     export JEKYLL_LOCAL_ROOT="$HOME/Sites/jekyllsite"
     export JEKYLL_REMOTE_ROOT="user@server:/path/to/jekyll/root"
     [...]

and other nginx git_host or rvm stuff. I think you know what i mean. Wouldn't it be better (and maybe more user friendly) if such things are separately placed in lib/jekyll.bash oder in plugins/jekyll.plugin.bash ?

When a new user downloads bash-it, he will see plugins or lib files and remove the ones he doesn't need. thats all. otherwise he got to edit .bash_profile and things as well. this were at least my first steps with bash-it

i think .bash_profile should contain only the basic and general things which are required to use the framework.

just my 2 cents ;)

[ghost]

My first steps were different, I went to editing my .bash_profile straightaway. And I think that others might rather it be consolidated into one file rather than have to go through multiple files just to find what they need.

[revans]

The point of the config (bash_profile) is so each person can setup these global vars to suit their systems needs. If one isn't using them or has a different location/name it's easy enough to change it in 1 file. (remove, edit, comment out, etc)

Also, if people want to contribute back (which was my hope from the beginning) I wouldn't want them sending pull requests where they had removed a bunch of files from the project itself.

[noqqe]

okay, i haven't thought about this point of configuration yet.
sounds useful too.