Stop allowing configurable z and zo commands #109
Closed
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.
This implements what we discussed here: #107 (comment). By moving to a static command we can ship the command and its completions in the format that fisher expects. This isn't just useful for fisher, it also works better with fish. By shipping static commands fish can lazy load both the commands and their completions. This means we don't have to run setup for this in conf.d scripts. It also simplifies the code a little bit.
Users can still easily create an alias fn, which is the canonical fish way of renaming a command. That way, even if they want to alias the command they can still retain the lazy loading.
Also, I took a look with grep.app, and could find only two users who were using a custom z command: see here. So this seems ok to change if we want to.