Skip to content

docs(README): elaborate and typofix command_not_found_handle FAQ item #774

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 15, 2022
Merged

docs(README): elaborate and typofix command_not_found_handle FAQ item #774

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -254,13 +254,15 @@ A. Probably because the database is being queried every time and this uses a
unless it detects that the database has changed since the file was created,
in which case it will still use the database to ensure accuracy.

**Q. bash-completion interferes with my `command_not_found_handler` function!**
**Q. bash-completion interferes with my `command_not_found_handle` function
(or the other way around)!**

A. If your `command_not_found_handler` function is not intended to
A. If your `command_not_found_handle` function is not intended to
address (possibly missing) commands invoked during bash
programmable completion functions, you can account for this
by, for example, testing if the `$COMP_`\* variables are set and
taking appropriate bypass or other action.
in the function by, for example, testing if the `$COMP_LINE`
variable is set and taking appropriate action, typically returning
early and silently with success.

**Q. Can tab completion be made even easier?**

Expand Down