-
-
Notifications
You must be signed in to change notification settings - Fork 803
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
Is a ~/.ignore (or ~/.fdignore) file always looked at? #485
Comments
Thank you for the feedback. The README example is just wrong (or at least very misleading) and should be changed. A
Yes, it can be very confusing. The behavior is quite complex, but it is very well thought out (this is all part of the Here is how we set up the Lines 71 to 103 in 59c27ba
If someone want's to spend some time to properly document this, it would be very appreciated. |
OK, this helps, thank you. There is no way to have a global ignore file like What is the alternative? |
We could also think about adding such a global |
Ah, right. |
Along the same lines, would you consider a |
ah yes, I would have assumed that "git-ignored folders" would include my global "gitignore" file. And the code:
looks like it could be supported |
Ah, the directory that produced the unexpected result did not contain a |
RigGrep supports a |
I'd love to see that feature, is there any progress? |
I don't think so. This should be rather easy to implement, though. |
The README shows the following example:
On macOS I tried creating ~/.ignore and also a ~/.fdignore symlinked to ~/.ignore with the following in it as I'm trying to avoid mounted/network file systems when using
fd
fromfzf
:The expectation based on the README example if I just
cd / && fd -t d keybase
is to not return/keybase
or/Volumes/Keybase
but they are returned which makes me think that ~/.ignore or ~/.fdignore are not looked at.If I'm explicit about using the ignore file
fd --ignore-file ~/.ignore -t d keybase
then it seems to work.Not sure if this is a bug or expected behavior. It is very hard to tell as there's no documentation that lists the expected behavior, it's all very confusing.
I understand there have been a lot of discussions around ignore, it may be worth having a table of expected behavior then people can work from there when reporting issues.
The text was updated successfully, but these errors were encountered: