You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: