{"issue":{"state":"closed","pull_request":{"diff_url":"https://github.com/revans/bash-it/pull/81.diff","html_url":"https://github.com/revans/bash-it/pull/81","patch_url":"https://github.com/revans/bash-it/pull/81.patch"},"milestone":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/ce1b70e933ccd810d7ea019b3369919f?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"ce1b70e933ccd810d7ea019b3369919f","url":"https://api.github.com/users/jfsiii","login":"jfsiii","id":57655},"updated_at":"2011-10-30T00:02:19Z","labels":[],"assignee":null,"comments":7,"closed_at":"2011-10-29T23:57:36Z","url":"https://api.github.com/repos/revans/bash-it/issues/81","body":"`$BASH` holds the pathname to the executable. See http://www.gnu.org/software/bash/manual/html_node/Bash-Variables.html#Bash-Variables","html_url":"https://github.com/revans/bash-it/issues/81","title":"Replace `$BASH` with `$BASH_IT` b/c `$BASH` is already present on *nix","number":81,"id":1688740,"created_at":"2011-09-20T15:21:22Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/7d3121c813ff3c3577324a096fe9a5c6?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"7d3121c813ff3c3577324a096fe9a5c6","url":"https://api.github.com/users/tswicegood","login":"tswicegood","id":4328},"updated_at":"2011-10-30T00:02:19Z","url":"https://api.github.com/repos/revans/bash-it/issues/comments/2567644","body":"I've merged this in with a few changes.\r\n\r\n* In the absence of `BASH_IT`, it relies on `BASH` and resets `BASH` to the original value\r\n* In the absence of `BASH_IT_THEME`, it uses `BASH_THEME` and unsets `BASH_THEME`\r\n* I moved the loading of themes back up to its original position.\r\n\r\nThe last one I'm not sure on why it was moved.  Seems to be functionally the same based on the commits, but stands a chance to break plugins and custom scripts inadvertently.\r\n\r\nRegarding the comment on how long to maintain BC, I'd like to maintain it as long as possible.  Since bash-it doesn't have releases, the idea is that pulling in code to your `~/.bash_it` directory should just upgrade you to the latest w/o causing anything to break.  At some point, we should probably add a warning message to tell people to upgrade, but for the time being I think the solution we've got works good enough since we reset `BASH` to its proper value as soon as possible.\r\n\r\nThanks for the fix.  Sorry it took so long to get merged in.","id":2567644,"created_at":"2011-10-30T00:02:19Z"}}