Félix Saparelli

~~Well, there's time to reconsider. v2.0 won't be anytime soon.~~ More importantly, [Windows 7 has not been supported since 1.3.0](https://github.com/watchexec/watchexec/issues/56).

Default _will_ change at 2.0.

Partial implementation in 1.18.0: - no colours - a message is only printed on non-success return More improvements are likely!

This essentially involves computing and caching a checksum for every file that's seen. Not a hard problem, but has interesting implications.

> ambiguous: The file content on the filesystem as shown by the Kernel is meant. Is it ambiguous? The OP says > when the contents of a file actually changed...

Right, I've looked at the logs, and there's something interesting happening which I think is an issue with globset. Relevant section, edited to be readable: ```yaml watchexec::action: got event event=Event...

You can't use `-f` for this but you can use `-e html` instead with a pattern like this: ``` watchexec -p -w dir -e html -i 'dir/*/**/*' ```

I wrote [a StackOverflow answer](http://stackoverflow.com/questions/7830675/how-can-i-preload-a-page-using-html5/7830732#7830732) for this a while back… and it's pretty comprehensive. tl;dr: - Link prefetching is [spec'd](http://www.w3.org/TR/html5/links.html#link-type-prefetch). - Firefox supports it from 3.5 but only on ``,...

I updated my SO answer today: http://stackoverflow.com/questions/7830675/how-can-i-preload-a-page-using-html5/7830732#7830732 TL;DR: Prefetch has very good support, DNS Prefetch has near-universal support, the other three (`preconnect`, `prerender`, `lazyload`) have varying levels of support. I'd...

Hi! Very interesting in nftables support... any updates on reviewing this PR?