unusual implementation of find command

[cbertelli]

Maybe it's a stupid request but the find command is not consistent with the usual syntax of the same command on unix like machines.
This implementation works with -p parameter for the starting directory, which is maybe good for windows.
Posix implementation uses the starting directory as the first parameter ("./" if starting from current directory) and the search pattern as the second.
It's not a big problem, but if you could detect the environment and switch the parameters, it would be convenient...

[CrispStrobe]

yes posix style is better, thanks. changed. also added (fuzzy) search.

[cbertelli]

Thank you. It works very well and it's relatively fast. Much better than using the native find on a mounted webdav drive and the fuzzy search is really effective.
It's very near to the posix find, but the syntax is missing the most common option -name "pAttErn*" for case sensitive search, -iname "pattern*" for case insensitive search. I think it's not advisable to try to implement a full find command inside the client, but I think it would be better to declare that the search is not case sensitive.

[CrispStrobe]

we could to that i think. it should work now with e.g. python cli.py find . --iname "*.jpg" --maxdepth 2

[cbertelli]

The posix option is with a dash only, -iname, but the implementation works well. Thanks