We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$ rg --version ripgrep 12.0.0 -SIMD -AVX (compiled) +SIMD +AVX (runtime)
Also,
$ git --version git version 2.25.1
Homebrew
macOS. Also seems to occur on Linux.
When running ripgrep on a git clone with submodules, it prints the following error:
$ rg -i foobar ../../../../.git/modules/path/to/submodule/commondir: No such file or directory (os error 2)
I suspect this is related to #1446
git init foo git init bar cd foo touch file git add file git commit -m 'initial commit' cd ../bar touch file git add file git commit -m 'initial commit' git submodule add ../foo path rg string
The ripgrep invocation will print
../.git/modules/path/commondir: No such file or directory (os error 2)
No warnings. Never warnings.
The text was updated successfully, but these errors were encountered:
34edb81
Oof, sorry. You're right. This is a regression.
I will put out a new release soonish. I'll give it a few days in case any other regressions pop up.
Sorry, something went wrong.
ignore: fix failing test
8ba6ccd
This fixes fallout from fixing #1520.
Any chance you could cut a release now? This issue is driving me batty!
I'd recommend just building from source if it's that bad. Otherwise: https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#release
I've released ripgrep 12.0.1 with a fix for this.
No branches or pull requests
What version of ripgrep are you using?
Also,
How did you install ripgrep?
Homebrew
What operating system are you using ripgrep on?
macOS. Also seems to occur on Linux.
Describe your question, feature request, or bug.
When running ripgrep on a git clone with submodules, it prints the following error:
I suspect this is related to #1446
If this is a bug, what are the steps to reproduce the behavior?
If this is a bug, what is the actual behavior?
The ripgrep invocation will print
If this is a bug, what is the expected behavior?
No warnings. Never warnings.
The text was updated successfully, but these errors were encountered: