-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Option to consider only parent .rgignore files? #53
Comments
Why not just whitelist the files you want to search in your (I think I had the same problem as you, so I just put |
Before whitelisting:
After whitelisting by add
I believe this works (just that this repeats the bug in #50). Thanks, I only concern is that if you implement a global ignore file in Then I would need to put On the other hand, if I put |
It seems like the priority of any "global" ignores file should come strictly after any ignores from inside parent directories are considered. If you want to override |
It sounds like this use case should be solved either by a global ignore file (#45) or by using explicit per-directory overrides. |
I have a
~/.gitignore
and that is considered as an ignore file for everything in my$HOME
. In my use case the contents of~/.gitignore
do not apply as ignore criteria for searches! I have~/.gitignore
set up just to prevent committing sensitive text files to git (and then push) by mistake. So that file contains something likeThat would prevent search of all
a*
files everywhere in my$HOME
.So it would be great to allow parent
.rgignore
(only) file consideration.In addition a
.gitignore
specific-u
would also be needed.In summary, there is very little overlap of the contents of
.gitignore
and search ignore files like.agignore
and.rgignore
.For
.gitignore
:.gitignore
For
.rgignore
:.rgignore
filesFrom what I understand, right now
-u
and--no-ignore-parent
applies to both of these files and you cannot set those options separately for those 2 files.The text was updated successfully, but these errors were encountered: