Is -tf -td -tl -ts -tp always true?

[x-yuri]

What version of fd are you using?
fd 8.3.0

I'm trying to exclude sockets so that tar wouldn't complain. And pipes since I don't need them. Should I use -tf -td -tl?

[tmccombs]

I think that -tf -td alone would match everything, because it matches all files and all directories.

[x-yuri]

Actually no:

$ mkfifo p
$ touch a
$ ln -s ./a b
$ fd -tf
a
$ fd -tl
b
$ fd -tp
p

Here are the corresponding lines:

fd/src/filetypes.rs

Lines 32 to 36 in 52f2255

	(!self.files && entry_type.is_file())
	|| (!self.directories && entry_type.is_dir())
	|| (!self.symlinks && entry_type.is_symlink())
	|| (!self.sockets && filesystem::is_socket(*entry_type))
	|| (!self.pipes && filesystem::is_pipe(*entry_type))

And the is_file description says:

Tests whether this file type represents a regular file. The result is mutually exclusive to the results of is_dir and is_symlink; only zero or one of these tests may pass.

Then the following lines suggest that the options in the title aren't true for every entry:

fd/src/filetypes.rs

Lines 43 to 47 in 52f2255

	|| !(entry_type.is_file()
	|| entry_type.is_dir()
	|| entry_type.is_symlink()
	|| filesystem::is_socket(*entry_type)
	|| filesystem::is_pipe(*entry_type))

So, I guess zero or one of those should match. But if zero, what are the other possible cases?

[tmccombs]

But if zero, what are the other possible cases?

That depends on the operating system, and possibly filesystem. On linux I believe that would include character and block special devices. Probably other special file types as well.

[tavianator]

On Linux I think block and character devices are the only other file types. The BSDs and macOS have "whiteout" files. Solaris and its descendants have "door" and "event port" files.

[sharkdp]

@x-yuri Can this be closed? Or do you think we could improve the documentation?

[x-yuri]

I think yes. UPD Noticed the part about the documentation. I'm not sure. It's up to you.