Re: Inconsistent behavior of core utilities

[L A Walsh]

On 2022/08/23 00:30, Mike Jonkmans wrote:
> > que
> >     
>
> find is the path to go.
>   
Because find isn't part of coreutils?

find isn't consistent either:

find . -name \*.foo

gives you output from dir ".", but you have to edit the output or add 
other args to
get just the filenames, since there is no easy way to start from the 
current directory:

find -name \*.foo

gives the same output as the 1st example, and trying to specify the 
current dir another way, also fails:

find "" -name \*.foo
find: ‘’: No such file or directory


find isn't the path to go, as it's internally inconsistent (not to 
mention it's not
part of coreutils).