Add support for ripgrep (rg) #36
Merged
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
geksilla
approved these changes
Sep 27, 2016
|
Cool. I will also try ripgrep. Thanks for contribution! |
|
@geksilla please publish to atom packages so I too can try ripgrep! Thanks! |
|
@xhn35rq, published new version. |
|
Many thanks |
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.
Ripgrep is a new grep-like tool written in Rust and has gotten some buzz lately. With the right flags, it produces output that is consumable by fuzzy-grep.
Here, I followed #21 on some small code changes.
When I tried this yesterday, it wasn't working due to an IO issue (BurntSushi/ripgrep#35), but I confirmed that the current HEAD works and should work by the next release
(0.1.18)(0.2.0).