New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bash auto complete does not display all possible tasks for my system. #80

MattSeen opened this Issue Jun 30, 2015 · 0 comments


None yet
1 participant
Copy link

MattSeen commented Jun 30, 2015


Love this tool. It's really awesome and I appreciate the auto complete script you threw in for it. The only trouble is, I recently rewrote a build system from being a really, really big un-maintainable single grunt file to a modular system by using the plugin load-grunt-config and jit-grunt. These are great plugins for making a clearer a more maintainable build system as we grow it overtime. The only trouble is that breaks the assumption of the bash auto complete script.

This is the line that causes my issue

# The current grunt version, available tasks, options, etc.
local gruntinfo="$(grunt --version --verbose 2>/dev/null)"

Now if this line were to read grunt --version --verbose --tasks I would be in business . As an aside, running grunt with a --tasks flag and not provide it an input causes an error on my system, but that is probably a wider issue.

Basically I don't really know what would be the best approach to resolve this issue. You should probably provide a way for people to specify those additional parameters to the auto complete script. What that would look like I don't really know. Maybe an environment variable? Perhaps you allow me to have grunt run a script I would write and maintain, but then I can see other people having this issue in the future as well. And you know, open source or whatever.

I may have written myself into a corner on this because of the way those plugins work, but I'm pretty sure there could be some sort of solution for this. Any thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment