Skip to content
Browse files

fix for issue #136

issue #136 was found to be caused by an aliased 'ls' command that
generated rogue values for 'plugin' in the enable/disable-plugin()
functions. this commit fixes that by forcing the shell to disregard
aliased 'ls' commands.
  • Loading branch information...
1 parent 566bfbc commit c7207cb34f6ce36b2663df57f9e35b03e643fd79 @erichs erichs committed with May 20, 2012
Showing with 2 additions and 2 deletions.
  1. +2 −2 lib/helpers.bash
View
4 lib/helpers.bash
@@ -74,7 +74,7 @@ disable-plugin ()
fi
done
else
- typeset plugin=$(ls $BASH_IT/plugins/enabled/$1.*bash 2>/dev/null | head -1)
+ typeset plugin=$(command ls $BASH_IT/plugins/enabled/$1.*bash 2>/dev/null | head -1)
if [ ! -h $plugin ]; then
printf '%s\n' 'sorry, that does not appear to be an enabled plugin.'
return
@@ -107,7 +107,7 @@ enable-plugin ()
fi
done
else
- typeset plugin=$(ls $BASH_IT/plugins/available/$1.*bash 2>/dev/null | head -1)
+ typeset plugin=$(command ls $BASH_IT/plugins/available/$1.*bash 2>/dev/null | head -1)
if [ -z "$plugin" ]; then
printf '%s\n' 'sorry, that does not appear to be an available plugin.'
return

0 comments on commit c7207cb

Please sign in to comment.
Something went wrong with that request. Please try again.