Pawel Knap

Hey @nohupped , this is a bug in `notify` logic. Since inotify sends only file names, we store full paths in memory. However, when directory is moved, these paths are...

> A means to detect all events that correspond to a removed file (either due to deletion or renaming/moving to another path/filename). @imsodin you may create a workaround, specific only...

> A means to match two rename events on all supported platforms. This is also possible on windows but hasn't been implemented in `notify` yet. We can tie rename file...

> Is my assumption incorrect that these two actions are equivalent? They are, We probably need to make them consistent in some future. The reason why this was done in...

@imsodin all events can be bitmasked - that's the reason why we have these bit shifts there. You can safely: ```go const removeEventMask = notify.FileActionRemoved | notify.FileActionRenamedOldName ```

Just to explain mapping of Windows file actions to notify events: ``` FileActionAdded = 1

@imsodin yes, windows has different logic than other watchers, you must register [filters](https://github.com/rjeczalik/notify/blob/master/event_readdcw.go#L32) eg. `notify.FileNotifyChangeFileName`, `notify.FileNotifyChangeDirName` in order to get actions. More info [here](https://msdn.microsoft.com/en-us/library/windows/desktop/aa365465(v=vs.85).aspx)

This is rather a question for @rjeczalik . Personally, I think it would be a nice doc improvement and, of course, any kind of help on this project is always...

Hi guys! @timesking I assume that want to receive create events for `/c/b/1.txt` and `/c/b/2.txt`. The problem is that these events are triggered **before** we create watchers for `c` and...

@lsegal Thanks for reporting this. It definitely looks like a bug since there shouldn't be any difference between watching root directory and any other path.