Warn when forgetting --hidden on a filename starting with .

[jannikschaper]

First time fd user, just took 3 minutes to figure out why fd won't find my .eslintrc.js file; see shell history:

fd
fdfind
fdfind .eslintrc.js
fdfind *.eslintrc.js
fdfind \*.eslintrc.js
fdfind \.*\.eslintrc\.js
fdfind --globl "*.eslintrc.js"
fdfind --glob "*.eslintrc.js"
fdfind --glob "**/*.eslintrc.js"
fdfind | grep ".eslintrc.js"
cd ci
fdfind
fdfind -a
fdfina --help
fdfind --help
fdfind --hidden .eslintrc.js

Yes it's a rookie mistake, but it also wouldn't hurt anyone I think if fdfind detected this mistake and wrote a heads-up message to stderr :)

Specifically: when a pattern is specified where any possible match would be implicitly filtered out, for example by the implicit --no-hidden, or others, if there are more cases like this

[tavianator]

The main complication is that patterns are regular expressions by default, where . means "any character" not "a dot". The expressions are also unanchored, meaning your .eslintrc.js pattern would match Aeslintrc.js.gz, foo.eslintrc.js, etc. I think warning every time the first pattern char is . would be too much. We could warn on

fd '^\.foo'

[jannikschaper]

Yes, definitely, that's what I meant

And fd --glob .foo should get a warning too, because --glob also seems to anchor to the filename start