docs: update sub-command regex to support ranges #18
Conversation
This file contains 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
With this added regex the sub-commands will auto-complete even when using ranges.
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.
I have a personal Neovim plugin that lets me quickly jump from Neovim into GitHub PRs and blames based on commit shas, numbers, or search queries. My first version had a bunch of root-level commands. Then I read your guide, and subcommands are easy to implement now! So I did it! Thanks for writing it. I learned a ton.
My commands use ranges, and I realize the example doesn't support them. Maybe adding them to the example would be nice, even if the
Rockscommand doesn't use ranges.