08 Jun, 2012
3 commits
-
The `name` argument will be phased out. Instead, the btype will indicate the
type of a plugin. Currently it can have valuse of plugin and theme.
07 Jun, 2012
10 commits
-
It looks like bundle-apply is not required anymore. Now that we call `compinit
-i` at the end of `bundle-install`, we shouldn't need this. Every time a new
bundle is added by the user that defines completions, the `bundle-install` the
user runs, should create the `.zcompdump` with the new completions too. But I'll
keep this here, probably deprecating after some further investigation. -
And a couple of fixes for bugs discovered along the way. These are tests *only*
for the valid syntaxes. Its currently undefined behavior for invalid syntaxes.
Tests for proper error reporting should also be added soon. -
Tests are currently failing and already helped me spot a bug with the argument
parsing (That's where the tests fail).
06 Jun, 2012
5 commits
-
The previously used two variables ANTIGEN_REPO_CACHE and ANTIGEN_BUNDLE_DIR are
now replaced by a single variable, ADOTDIR. Defaults to `$HOME/.antigen`.
05 Jun, 2012
21 commits
-
The `bundle-list` command is used to list the currently specified bundles.
-
Where there are no bundles, or the bundle directory does not exist, the
`bundle-cleanup` command gives out an error. This fix is to make it give a saner
message instead. -
Current theme and the plugins installed on-spot in current session should not be
listed in the cleanup list. They were because of a problem with updating the
`$bundles` record. This is now fixed.If the above `if` is directly piped to the below `while`, the contents inside
the `if` construct are run in a new subshell, so changes to the `$bundles`
variable are lost after the `if` construct finishes. So, we need the temporary
`$install_bundles` variable. -
This message comes up every time you switch the prompt theme.
-
compinit needs to be loaded at startup too, or the compdef function won't be
defined. -
bundle-init is now renamed to bundle-apply and is to called after all bundle
specifications are given. Also added notes in the README file.The reason is the compinit function needs to be run after adding all the
required directories to `fpath`. The only reliable and performant way to do it
would be to explicitly call a function that does it after specifying all the
bundles. -
The -T is not really required here as we're checking and deleting
the target if it already exists. -
This particular plugin does not provide a completion file with the same name as
the plugin name, but does provide completions for a number of other commands.
So we just add all plugin paths to fpath.See https://github.com/sharat87/lawn/issues/1
04 Jun, 2012
1 commit
-
Instead of making a copy and fixing problems with it (like copying/excluding
.git), we now simply create a soft link to the plugin location.