fd

matches a pattern against the absolute path instead of the relative one. This is not well documented and it's a possible cause of confusion (e.g. #769). In my opinion, it is also less ergonomic than matching against the relative path of a candidate. My suggestion is: Replace with to make it clear this matches against the absolute path Add a new flag to allow matching against the relative path Thank you for the great work and for your focus on usability!

Overview Currently, can filter hidden/ignored files from search results according to the following flags: , , : Show/omit search results from files and directories ignored by rules/patterns in '.gitignore', '.ignore', '.fdignore', or the global ignore files. , : Show/omit search results from hidden dot files. : Show both the ignored and hidden files. This gives us two kinds of results: 1. A "restricted" mode with the paths matched by the search patterns but without the files/folders in hidden/ignored paths. 2. A "mixed" mode with all the paths matched by the search patterns, disregarding when it is or isnt't in a hidden/ignored path. Proposal Add a new flag like to filter out files/folders that are not under ignore/hidden paths. This will yield a third mode where the search result will omit "restricted" entries but will show files/folders that are under ignore/hidden paths. This new flag can also be combined with flags and to further restrict the search results. Use cases Searching only in hidden folders like () Searching only non-committed files under rules in Git repositories