Using a short name like ff makes me very hesitant to install this tool. Such convenient names should be reserved for user aliases, not for any program to claim. I suggest you change the binary's name to ffind, and add a simple alias ff=ffind to the installation guide.

Be able to exclude directories without using a regular expression.

Description

There is an ambiguity between a file or folder. A file can have no extension, so there is no way using a regular expression to distinguish between a file or a folder.

e.g. /home/user/ambigous_name

is it a file, or a folder? because ff will output this and there is no regular expression that can guarantee this to get filtered.

I did a simple test that gets the following output.

dev@rasp03:/home/dev/test $ ff .
.
./this_is_a_file
./this_is_a_folder

Motivation

The reason for this is that I want to replace the default vim command for https://github.com/ctrlpvim/ctrlp.vim extension (for obvious reasons).

I am using the following, actually.

let g:ctrlp_user_command = 'ff . %s -x "/$"'

But unluckily it also includes directories. As an example, the default command will be the following.

let g:ctrlp_user_command = 'find %s -type f'

It could be a good start point as choicing the way/parameter name for this.

Final

If you find this is already implemented or not relevant, please let me know so I can look for a workaround, and also thanks for this great tool!

Test env:

• at my home dir, searched for ff ssh

• ./.ssh/id_rsa.pub was not found, for example

• with find . | grep ssh

• it was.

IMHO to include hidden dirs should be the default behavior (since I'm looking for it... and don't know where it is).

Maybe an argument --ingore-hidden-dirscould also be a nice thing (in which would present the current behavior)

In any case, it's a great tool and congratulations!

Cheers

Is this availlable for Windows 10? I can't find such a release asset.

I use fd. What is the elevator pitch for switching.
Thanks