Replies: 1 comment 2 replies
|
Your .fdignore patterns do not work because ignore files are relative-pattern files, not shell path expressions: ~ is not expanded there. Also, disabling all ignore processing with -I would disable .fdignore too. Use the narrower VCS-ignore switch and keep hidden-file filtering enabled: That stops reading .gitignore/.git/info/exclude/global Git excludes while fd still hides dotfiles and .git by default. If you also want selected hidden paths, add -H and explicitly exclude .git: To make this permanent, use a shell alias/function: or configure the equivalent default options in your preferred wrapper. A global fd ignore file can exclude .git when -H is used; on Linux/macOS it is normally ~/.config/fd/ignore and should contain: not ~/.git. The current README documents hidden handling, VCS ignore behavior, --exclude, and the global ignore path: Hidden and ignored files, global ignore. |
|
There is also the |
|
Good addition — --no-ignore-parent is the narrower option for this exact case. It ignores .gitignore, .ignore, and .fdignore files inherited from directories above the search root, while preserving ignore files at or below the directory being searched. My earlier --no-ignore-vcs suggestion disables VCS ignore handling more broadly. So when the unwanted rules come specifically from the home directory being a parent Git repository, the preferred command is: fd --no-ignore-parentThanks for pointing out the more precise flag. |
Uh oh!
There was an error while loading. Please reload this page.
The way I manage my $HOME is via git and subsequently unless I'm in a git repo I think https://github.com/kaihendry/dotfiles/blob/master/.gitignore is read by fd and I'd rather it didn't.
I tried
but it doesn't work. 😬
I don't want to pass
fd -HIeverytime I use it!All reactions