Bug: editing a file triggers all 3 events for same file

[e2]

How to reproduce:

1. edit file in Vim
2. the callback is called with e.g.:

:modified=>["foo", "4913"], :added=>["4913", "foo"], :removed=>["foo", "4913"]

It makes no sense to have the same file triggering all(!) 3 events within a single callback.

The events should either be:

• "squashed" (so e.g. only "modified" is triggered)
• only 2 callbacks in the correct order (removed, added)

It doesn't make sense to have the same file simultaneously as:

• "removed" and "modified" (just "removed" or just "modified")
• "added" and "removed" (just "removed" or just "added")
• "modified" and "removed" (just "removed" or just "modified")
  etc...

Technically, this is obscuring the original information in a way where no client can piece things together (e.g. distinguish between a newly added file or modified-and-moved file) without keeping a complete shapshot of the filesystem between callbacks.

(I wanted to discuss this before even attempting a fix/pull request - in case there's stuff I don't know about)

[thibaudgg]

I agree that's a problem we need to fix that. I think it comes from how Vim is handling file saving, each editor has its own way (I guess you're on Linux): https://github.com/guard/guard/wiki/Analysis-of-inotify-events-for-different-editors

In that precise case, having only "modified" would be great.

[e2]

Fixed in #212