Skip to content
This repository

Apr 28, 2014

  1. cceleri Patched changes made to support custom.*.bash files.

    Code was added to support loading
    custom.{aliases,completion,plugins}.bash from their respective
    directories in 46f6701. The change made in that commit does not wait
    until the enabled {aliases,completion,plugins}/*.bash files are loaded
    before sourcing the custom.*.bash files, which was the case before. This
    patch fixes any issues caused by that change by loading the enabled
    *.bash files and custom *.bash files in two successive for loops.
    cceleri authored

Apr 24, 2014

  1. cceleri Added support for custom.plugins.bash and custom.completi…

    cceleri authored

May 23, 2012

  1. Nils Winkler

    Merged @erichs changes for the bash-it function.

    nwinkler authored

May 14, 2012

  1. Erich Smith

    update help documentation

    erichs authored

Apr 28, 2012

  1. Erich Smith

    import composure functions

    erichs authored

Apr 17, 2012

  1. grimreaper

    Fix bogus bash binary location

    grimreaper authored

Mar 26, 2012

  1. Travis Swicegood

    Extract loading of enable-able files and add reload_* functions

    tswicegood authored

Oct 29, 2011

  1. Travis Swicegood

    Make sure that the new BASH_IT/BASH_IT_THEME maintains BC

    tswicegood authored
  2. Travis Swicegood

    Move this back to its original location

    Not sure why this needs to be moved.  Feels like it could cause some
    issues since the values defined in themes aren't available to any of the
    lib or plugins.
    tswicegood authored
  3. Travis Swicegood

    Merge remote-tracking branch 'jfsiii/master'

    tswicegood authored

Oct 28, 2011

  1. John Schulz

    `$BASH_IT` should be conditionally defined before use.

    7483c6d moved one line too many.
    jfsiii authored

Oct 27, 2011

  1. John Schulz

    Custom themes should be loaded *after* the base theme.

    jfsiii authored

Oct 10, 2011

  1. Jon Schewe

    Remove error message when enabled directory is empty

    This is fixed by checking if the file exists before trying to source it.
    jpschewe authored

Sep 20, 2011

  1. Replace `$BASH` with `$BASH_IT` because `$BASH` is already used on *n…

    John Schulz authored

Aug 22, 2011

  1. Noorul Islam K M

    Do not break out of the loop instead continue with other items in the…

    … list.
    noorul authored tswicegood committed

Jul 24, 2011

  1. Remove automatic creation of enabled plugins/aliases/completion

    Mark Szymanski authored

Jun 24, 2011

  1. Add support for multiple Jekyll sites

    Mark Szymanski authored

Jun 21, 2011

  1. Travis Swicegood

    Switch to single loop now that all directory use the same pattern

    Simple refactoring -- now there's no need to source each one
    tswicegood authored
  2. Travis Swicegood

    Move auto-complete code over to available -> enabled style

    This continues the move toward the ability to turn things off with
    everything turned on by default.
    tswicegood authored

Jun 17, 2011

  1. Make sure custom aliases file exists before sourcing it

    Mark Szymanski authored

Jun 14, 2011

  1. Can't forget to source the custom aliases!

    Mark Szymanski authored

Jun 13, 2011

  1. Travis Swicegood

    Make all aliases optional (a la plugins)

    This continues a pattern that was introduced in ffa45b0 and refined
    further in later commits.  This enables all aliases by default, but can
    be disabled by any user if they remove the appropriate
    aliases/enabled/*.bash file.
    tswicegood authored

Jun 06, 2011

  1. Added Homebrew aliases

    Mark Szymanski authored

May 28, 2011

  1. Fix issue with plugin initalization

    Mark Szymanski authored

May 27, 2011

  1. Initialize enabled directory if it doesn't exist

    This is to make bash_it work in a new install after
    the plugins/enabled directory was ignored
    Mark Szymanski authored

May 03, 2011

  1. Travis Swicegood

    Create the concept of enabled plugins

    This allows users to disable a plugin without completely removing it.
    Instead, they simply remove the `plugins/enabled/*.bash` file for the
    plugin they want to disable.  This continues the concept of "everything
    on" while providing greater flexibility to future users.
    It might be a good idea to allow turning these off by default in the
    future and allowing not only the `plugins/enabled/*.bash` files but also
    an array of `<plugin_name>` values that would search for
    `plugins/available/<plugin_name>.plugin.bash` to enable them.  That
    method would make it easier for people custom tune their plugins from
    within their `.bash_profile` script.
    tswicegood authored

Nov 11, 2010

  1. John Schulz

    Allow theming to be disabled (eg for old terminals)

     * Only load a theme file if `bobby` has been set
     * Only alter `PS1` if `\[[1;34m\]\[$(scm_char)\]\[[0;32m\]\[$(scm_prompt_info)\]\[[0;34m\]\[$(rvm_version_prompt)\] \[[33;40m\]\h \[[39m\]in \[[0;32m\]\w \[[39m\]\[\n\[[0;32m\]→\[[39m\] ` has a value
    jfsiii authored

Nov 10, 2010

  1. Robert Evans

    merge conflict

  2. John Schulz

    Theme changes

     * Load colors before base theme so they can be used by base theme
     * Change git-specific variables to SCM-agnostic ones
    jfsiii authored

Nov 08, 2010

  1. Florian Baumann

    added documentation for plugins-help

    noqqe authored

Oct 31, 2010

  1. Added todo-help entry in's bash-it function

    Mark Szymanski authored

Oct 12, 2010

  1. Robert Evans

    updated comment


Oct 10, 2010

  1. Robert Evans

    Made a lot of changes: no more functions directory. All aliases have …

    …been moved to the new alias directory. Plugins are now for functions only. Updated the README to reflect the changes and add a contributor's list.

Oct 07, 2010

  1. Robert Evans

    Removed custom.bash and am now completely ignoring all files within t…

    …he custom directory. Started de-macify to provide more support for linux (thanks to alsemyonov on github).

Oct 03, 2010

  1. Robert Evans

    Added a couple more themes and put colors into its own file

Something went wrong with that request. Please try again.