Rafał Jęczalik

@nathany Oh sorry, we were discussing it over e-mail - it's for `fsevents`.

@nathany The problem is if you set a watch on `/users/rjeczalik/test` then any incoming event will have a path with a proper case, `/Users/rjeczalik/test/test` in this case. Example: ``` go...

> Would it be possible to just fix /users/rjeczalik/test to the actual path at the beginning of Watch? Yup, that's the plan, we'll need `realpath` syscall for that.

Hey @F21! It's a known limitation of inotify (http://man7.org/linux/man-pages/man7/inotify.7.html): ``` If monitoring an entire directory subtree, and a new subdirectory is created in that tree or an existing directory is...

https://travis-ci.org/rjeczalik/notify/jobs/51878432

@JK-97 What OS is that? Can you build your application with debug tag and run it again?

@JK-97 Yes and no, if you rm -rf then you're going to receive remove events for each deleted dir and file, but you shouldn't receive duplicated events on the same...

@hnakamur There's definitely room for improvement here. If you're expecting high volume of events you may find `QueuedWatch` helpful - https://gist.github.com/rjeczalik/7faa93691e6da35b1f84, and eventually do coalescing of the events in your...

> How about changing this to > func Watch(path string, c chan

@pzreact Is it a panic? What does it say? Where are the sources for your go program?