-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
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
Unsure how to search with wildcard paths #79
Comments
The difference between CLI Long story short, you should use Does that work for you @comatory ? |
Did you mean type it like this into telescope? Because that did not work for me. Can I check somehow that telescope is indeed using |
As soon as I add
Ok running it gave me this:
Does not look like I have this set up inside of
I definitely have |
Description
I'm used to using
ag
with searching like this `ag "some.*regex" path/**/some-subfolder. When I trigger the search window and type:"some.*regex" path/**/some-subfolder
I don't get any results. I checked the query with
ag
on command line and I get results. This is how my telescope is set up:In order to get results I have to specifically narrow down the path with specific subdirectories. Perhaps I'm not really searching with
ag
? I'm not sure how I could find out.I use
lazy.nvim
as my package manager.Thanks for any suggestions.
Neovim version
Operating system and version
macOS 14.3.1
Telescope version / branch / rev
e9e01d699843af530ef4ad2c8679a7e273bb3dd1
Telescope live grep args version / branch / rev
731a046
checkhealth telescope
Steps to reproduce
<C-k>
"<your regex here>" <path>/**/<subdirectory>
Expected behavior
Get the same list of files as if launching it with command-line:
ag "<your regex here>" <path>/**/<subdirectory>
Actual behavior
No files present
Minimal config
The text was updated successfully, but these errors were encountered: