4 ms·

Whatever version of find I have installed, it's an incredibly bad actor: > $ find --help > find: illegal option -- - > > $ find -help > find: illegal

Whatever version of find I have installed, it's an incredibly bad actor: > $ find --help > find: illegal option -- - > > $ find -help > find: illegal option -- h > > $ find -h > find: illegal option -- h I say "whatever version" because I cannot find that out either. A bare `find` doesn't tell me and I get similar non-support for --version / -v.

slightwinder 2y ago
Have you tried finding its path and looking into the file itself? Maybe it's a wrapper or alternative version somewhere in your $PATH you installed and forgot? And to add some mor efor testing: you can try "find /help", "find /?" and "find -?", in case it's using dos-style parameters.
- oneeyedpigeon 2y ago
  > $ file `which find` /usr/bin/find: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64e:Mach-O 64-bit executable arm64e] > $ find /help find: /help: No such file or directory > $ find /? zsh: no matches found: /? > $ find -? zsh: no matches found: -?
  - achierius 2y ago
    If you have brew you can install findutils to get gfind which behaves more like you'd expect
  - slightwinder 2y ago
    Is this MacOS? As I remember, they are using the tools from freebsd, and according to man-pages I randomly found on the internet it has indeed no help-parameter. I guess, their culture is to use "man" instead of flavors of --help.
gregjor 2y ago
You have a manky version or an alias over find somewhere. On my system Ubuntu 24.04: $ find --version find (GNU findutils) 4.9.0 $ find --help works $ find -help works $ man find then /help works