A common mistake involving wildcards and the find command

Re:A common mistake involving wildcards and the find command by kragen on Saturday February 08, 2020 @05:58PM (#22279191)

Wouldn't you have the same problem with fd if you invoke it on unquoted globs? The problem is the semantics of the shell, not find.

[ Parent | on HN ]

Re:A common mistake involving wildcards and the find command by wffurr on Saturday February 08, 2020 @06:24PM (#22279331)

Yes, but fd has implicit pattern matching without requiring the * character:

    Features:
        Convenient syntax: fd PATTERN instead of find -iname '*PATTERN*'

[ Parent | on HN ]

Re:A common mistake involving wildcards and the find command by pwdisswordfish2 on Sunday February 09, 2020 @05:12AM (#22281357)

Seems a misfeature. Much of the time, I use find to look for files with a specific extension, which makes the trailing asterisk harmful.

[ Parent | on HN ]

Re:A common mistake involving wildcards and the find command by johnp_ on Sunday February 09, 2020 @07:18AM (#22281747)

    fd -e py

Also neatly bypasses the glob issue.

[ Parent | on HN ]