Can file searching be faster and more efficient with ugrep than with fd?

I would think so, since find doesn't appear to search in parallel like ugrep does.

ugrep and find are different beasts through. Running ugrep with a glob (see previous response) and then --filter can run the specified --filter command on the files found.

For example, ugrep '' -g'*.txt' --filter='*:stat %' displays the stat output for all txt files recursively found.

Another example, ugrep -3 -c '' -g'*.zip' --filter='*:unzip %' will expand all .zip files recursively up to 2 more subdirectory levels deep in the working directory (use unzip -t % to try out without expanding the files).

The --filter option is abused to do this (with * to match any file extension so -g just selects whatever you want). That's fine. For the second example I used -c to output the number of lines produced by unzip. Using -l to list may work, but there can be problems with the way this option terminates the pipe to the process early, without consuming all unzip output, thereby interrupting the unzip. Perhaps I should think of a way to avoid this and let -l (and -q) with --filter always consume all process output.

I'm sure some clever folks can come up with some examples for practical use cases to use --filter this way. If someone has ideas to push this further, then I very much like to hear more.

ugrep as find (fd) replacement #194

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions