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
Say I have two files in my workspace, ./foo/bar/file1.txt, and ./bar/foo/file2.txt. There seems to be an inconsistency in how the --glob option works:
./foo/bar/file1.txt
./bar/foo/file2.txt
--glob
rg -g 'foo/**'
rg -g '/foo/**'
rg -g '!foo/**'
rg -g '!/foo/**'
The .gitignore works as I'd expect:
foo/
/foo/
Am I using the CLI option wrong?
The text was updated successfully, but these errors were encountered:
80e91a1
No branches or pull requests
Say I have two files in my workspace,
./foo/bar/file1.txt
, and./bar/foo/file2.txt
. There seems to be an inconsistency in how the--glob
option works:rg -g 'foo/**'
searches both, also expectedrg -g '/foo/**'
searches file1.txt, which is expectedrg -g '!foo/**'
searches neither, which is expectedrg -g '!/foo/**'
searches neither, whereas I'd expect it to only exclude the file1 path.The .gitignore works as I'd expect:
foo/
excludes both/foo/
only excludes the file1 pathAm I using the CLI option wrong?
The text was updated successfully, but these errors were encountered: