Fix support for using ripgrep with vim-dispatch #276
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
Same as ag, [ripgrep](https://github.com/BurntSushi/ripgrep) supports a `--vimgrep` flag so that it can be used as `g:ackprog`. However, when used via `vim-dispatch`, stdin is not closed which ripgrep interprets as a pattern to be supplied and hence fails to execute anything. To disable this behavior, we need to explicitly supply a root-directory to start searching in.
obreitwi
added a commit
to obreitwi/dot_vim
that referenced
this pull request
Jul 18, 2021
To use ripgrep with ack, use own fork until mileszs/ack.vim#276 is merged.
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.
Same as ag, ripgrep supports a
--vimgrepflag so that it can be used asg:ackprog.However, when used via
vim-dispatch, stdin is not closed which ripgrepinterprets as a pattern to be supplied and hence fails to execute
anything.
To disable this behavior, we need to explicitly supply a root-directory
to start searching in.