Skip to content
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

An option for specifying the directory for ag or rg #81

Open
at8i opened this issue Dec 10, 2020 · 1 comment
Open

An option for specifying the directory for ag or rg #81

at8i opened this issue Dec 10, 2020 · 1 comment

Comments

@at8i
Copy link

at8i commented Dec 10, 2020

An option for specifying the directory in which ag or rg will parse through. I noticed that if I run ag or rg through my project's src directory(C++), it will map everything. Especially ag seems to work just fine without E474 bug. (E474 bug with rg but no bug with ag). The problem is ag is not searching the right directory . So if it was possible to let ag know which directory it should be searching, all the problems(AKA Bug E474 not working with rg) would go away or am I wrong?

@flwyd
Copy link

flwyd commented Feb 8, 2021

A couple things I'd love to see:

  • Determine the search directory from the file path. I noticed that if I'm in ~/foo/bar and I edit ~/project/src/code.py, any-jump doesn't find anything, since the code isn't in my working directory.
  • Ability to specify an explicit list of directories to search. I often work in a large monorepo; searching the whole thing with ag/rg is not possible, but they can comfortably search from a set of "project roots" that are of interest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants