Neil Mitchell

I'm investigating and writing some tests now, so hope to have a solution later this evening.

My results are in PR #31.

Thanks, that's probably a workable approach for the setup I'm in.

Looking at the bigbro API: - I agree that the order of operations is potentially important. I don't think it's that big a deal to the API though - just...

I actually don't have any uses where order is important, beyond the callback, where order is certainly important but obvious anyway. However, it seems like a file system tracing thing...

I think a callback is simpler. It's a C API - I expect it to segfault it if I upset it, so I don't see any problem with multiple simultaneous...

For order of events, its certainly going to be observable which order they are returned to the C user, so it makes sense (to me at least) to define that...

To somewhat echo @droundy's point, I don't really care what the underlying mechanism is, but I do want something that presents the same interface on all platforms (so I can...

Doing it on Windows is possible, but a bit of a pain. However, if the file changes names with each git revision, and has a known size, that might be...

So is the upper-case `R` relative thing something Shake should handle? And what is it relative to - the current directory at the time it was captured? Under which circumstances...