fd VS watchexec

Perhaps interesting (for some) to note that hyperfine is from the same author as at least a few other "ne{w,xt} generation" command line tools (that could maybe be seen as part of "rewrite it in Rust", but I don't want to paint the author with a brush they disagree with!!): fd (find alternative; https://github.com/sharkdp/fd), bat ("supercharged version of the cat command"; https://github.com/sharkdp/bat), and hexyl (hex viewer; https://github.com/sharkdp/hexyl). (And certainly others I've missed!)

Pointing this out because I myself appreciate comments that do this.

For myself, `fd` is the one most incorporated into my own "toolbox" -- used it this morning prior to seeing this thread on hyperfine! So, thanks for all that, sharkdp if you're reading!

Ok, end OT-ness.

However, if it catches too many typos in changelogs/README instead of the actual code, try using the fd command to specify file extensions or exclude directories. For example, the following command searches only for .cr files and excludes the lib directory:

Oh right, we didn't know this, most of the tools install guides have nix-env like fd, lychee, gtrash, etc and others we listed which we just use for installation.

https://github.com/lycheeverse/lychee?tab=readme-ov-file#nix...

https://github.com/sharkdp/fd?tab=readme-ov-file#on-nixos--v...

https://github.com/umlx5h/gtrash?tab=readme-ov-file#nixpkgs-...

Disagree all you want, you still shouldn't be surprised people aren't expecting this

fd: https://github.com/sharkdp/fd/issues?q=gitignore+

And I stand by it is strictly better for the __default__ to be unfiltered. This is what people expect in general.

  > tailored for the common use cases today.

NOTE OF WARNING:

BY DEFAULT these ignores anything included in your `.gitignore` folder. So if you think it is a straight find replacement, you'll likely be surprised. fd discussion here[0]

Just make sure that when recommending people these tools that this is clear because if they don't read the docs (lol who does) they'll miss this part.

This is a pet peeve of mine. I wish the people that make these replacement coreutils (and others) would leave the defaults as very similar to the original tool. I do really like the new functionalities but if you market it as "an alternative" ("It is a simple, fast and user-friendly alternative to find") then they should respect the defaults of the original because it reduces new user surprise. I mean aliases exist... So it is better to have in your ~/.${SHELL##*/}rc file to have `alias fd='fd --ignore'` than `alias fd='fd --no-ignore'`.

Side note/pro tip: use `\command` if you want to use an unaliased version. An example of this is that I have `alias grep='grep --color=always --no-messages --binary-files=without-match` but this can sometimes be problematic because the color option can change the character representation so if you pipe this into `curl` you will get errors. This is not the case in all piping, but it is a shocking and confusing experience when you first encounter it. You can validate this by `echo "Hello world" | \grep --color=always "Hello" | hexdump` and then `!!:s^always^never`

[0] https://github.com/sharkdp/fd/issues/612

1. fd command

find files: fd

Hi, I am using Watchexec (https://github.com/watchexec/watchexec/releases) to monitor folder changes, but I want to exclude some folders. What parameter should I use to perform the route exclusions?

Use https://github.com/watchexec/watchexec

There's something similar to this called watchexec, which you can have a look at https://github.com/watchexec/watchexec

Or use watchexec which will do 95% of what you need and you're not tied to nodejs.

watchexec

I use watchexec to automatically run the code when saved, you should customise this to your liking.

OTOH PowerShell will not keep watching and is one of the requirements. In the past I've successfully used watchexecrepo and inotifywaitrepo.

I prefer watchexec as it's cross-platform.