Nelo Mitranim

Hmm on second thought, `-i` probably wouldn't work in this case. The watcher will still try to access the directory. `gow`'s filter applies only to the already-received filesystem events. Your...

Main reasons I used `rjeczalik/notify` and avoided `fsnotify/fsnotify`: * `rjeczalik/notify` supports recursive watch out of the box. * `rjeczalik/notify` uses OS-specific FS notification APIs and avoids polling. It performs NO...

Before doing any reworks, it would be nice if I could debug this locally. There might be simpler solutions. I tried to reproduce this by altering directory permissions, but wasn't...

Thanks for the tip. Might be a good idea for multiple reasons. For example, one thing that keeps coming up is that not every Go user has `$GOPATH/bin` added to...

Since feaffc23622278acc701928bcc132a01a3bb94b5, `gow` requires Go 1.18 or higher.

Not sure if required... Both dependencies (`github.com/rjeczalik/notify` and `golang.org/x/sys/unix`) use C in Darwin builds, but MacOS should ship with the required tools installed (?). Unfortunately I'm not sufficiently familiar with...

Good to know. I might debug this properly when setting up the next machine (in months / years). For now, I'll probably try to drop one dependency as described above,...

Perhaps it should be the default behavior for `-c`? In build systems that run many watchers simultaneously, clearing the terminal on launch is hazardous.

Same here. I'm currently using `marked`, which I believe is the next smallest markdown renderer, at ≈21 KiB minified (non-zipped). Snarkdown at ≈3 KiB seems very promising, but the lack...

@Jonarod Try `marked` for now, much smaller than `markdown-it`.