Write some stuff in the README to speed up command_not_found calls #282
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It was taking me ~2+ seconds every time that I accidentally typed `gti` instead of `git`. This makes the `command_not_found` call similar to other systems (and probably faster than a lot of them.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It was taking me ~2+ seconds every time that I accidentally typed
gtiinstead ofgit. This makes thecommand_not_foundcall similar to other systems (and probably faster than a lot of them.If it's something that is wanted, I could put something in the current scripts that will auto-detect if the
~/.cache/nix-index-not-found/filesindex exists and to use that, otherwise fall back on the default~/.cache/nix-index/db path.