You mean because it uses foo=bar rather than --foo=bar? I don't know, it's not that weird.
I mean, find uses parentheses for forcing evaluation precedence, e.g. -foo -or \( -bar -and -baz \). That's pretty unusual.
I mean, find uses parentheses for forcing evaluation precedence, e.g. -foo -or \( -bar -and -baz \). That's pretty unusual.
$ find -type f .
find: paths must precede expression: `.'
$ git grep Congrats -i
fatal: option '-i' must come before non-option arguments
They just seem to produce a syntax error no matter where I use them. But if they have no purpose, then why not simply treat them as nonspecial characters?
E.g.
echo hello :-) ;
echo "hello" ":-)";
?