Skip to content
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

CommandNotFound -- enabling and disabling #27

Open
ghost opened this issue Oct 12, 2017 · 0 comments
Open

CommandNotFound -- enabling and disabling #27

ghost opened this issue Oct 12, 2017 · 0 comments

Comments

@ghost
Copy link

ghost commented Oct 12, 2017

CommandNotFound can be quite useful if you want to find out where a program may
reside. However had, it can also be noisy sometimes.

My suggestion would be to add --enable and --disable switches to it, to allow a user
to specifically disable or enable the CommandNotFound functionality.

When it is invoked, it can also specifically tell the user how to do the revert command
again such as:

CommandNotFound --disable

"Commands that were not found in the shell no longer give any hints."
"If you wish to toggle/revert this functionality, use the --enable argument."

Or something like that.

Sorry for filing it here, I do not know where CommandNotFound resides (I am writing
this on my non-gobo machine right now).

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

No branches or pull requests

1 participant