Review and upgrade filtering/ignores for intuitiveness

[passcod]

This is a new catch-all issue for "ignores are confusing" so everything gets linked up here for consideration when this is tackled.

[passcod]

In general, the main idea is globset crate 👎, ignore crate 👍, but that was discussed ages ago in #14 and decided against... but that was 5 years ago, so let's review that.

[passcod]

Something that will help is to provide in the Config all of:

• the calling working directory, that is the intuitive base for casual ignores
• the root, where, as per git ignore syntax, / is
• the command’s working directory, which may be different from both

defaulting to the OS-queried workdir for all of these

[passcod]

This is becoming more pressing due to breaks with globset >0.4.6, see watchexec/cargo-watch#176. Could also add workarounds just for that upgrade; will depend on what I feel like...

[dimaqq]

[not sure if this is the right place]
.gitignore doesn't work out of the box for me:

• .gitignore has a line /dist †
• I run watchexec -v -e js ls for testing
• when I touch dist/bundle.js the command is re-ran

†
/dist means to ignore a thing named dist and anything under it, but only for top-level dist;
for example foo/bar/dist is not ignored by git in this configuration.

[passcod]

@dimaqq This is fixed as of 1.18.

I'm going to close off this issue on 2.0, as both the globset and tagged filterers will then fulfill the requirements.