Commit Graph

14 Commits (e2e63c96621ea8f0486fece92dbe9ffcb2d44da1)

Author SHA1 Message Date
Erich Smith 08e439c4f0 update plugin management 2012-05-13 22:13:54 -04:00
Erich Smith 55e77deac1 standardize plugins, update metadata
add about-plugin metadata
chmod -x plugins
cleanup filenames to standardize on x.plugin.bash format
only plugin files intended to be executable from the command line should
contain a shebang line, and should be a+x.
2012-05-13 22:13:54 -04:00
Erich Smith 254d4459e2 basic plugin management
move plugin management functions into 'lib' group in helpers.bash
2012-05-13 22:13:54 -04:00
Erich Smith 248eb30e00 plugin-specific metadata
cite about-plugin metadata.  This could be retrieved later, say by an
install script or other helper function, with:

cat ~/.bash_it/plugins/enabled/base.plugin.bash | metafor about-plugin

In this way, summaries of each plugin may be provided to give newcomers
(like me!) an overview.

also, rewrote plugins-help(), which didn't work very well on my system.
It now dynamically queries composure metadata.
2012-05-08 23:40:24 -04:00
Erich Smith 5d32cf9a02 quote examples
prevent bash expansion and parsing of example code
2012-05-07 12:51:10 -04:00
Erich Smith 2086a053df fix typo 2012-04-28 10:40:16 -04:00
Erich Smith e3011c5ead more portable pass function 2012-04-28 10:35:01 -04:00
Erich Smith a3c3caa0ab help metadata for base plugin 2012-04-28 00:43:38 -04:00
Eitan Adler 3fc60b5358 Fix bogus bash binary location 2012-04-17 00:24:58 -04:00
Travis Swicegood ea0dc44c53 Switch to echo -e and use echo safe colors (fixes: #96) 2012-01-26 08:18:59 -06:00
Mark Szymanski ba8fde85eb Make gshuf alias checker work on other bash versions 2011-08-12 16:30:55 -05:00
Mark Szymanski 576434048b Add simple password generator 2011-08-10 18:49:20 -05:00
Mark Szymanski 4898fa9119 Add pmdown function for previewing markdown files 2011-05-27 11:47:55 -05:00
Travis Swicegood ffa45b0391 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.
2011-05-02 23:12:50 -05:00