Jed Richards

Aha yes, nice one. That's simpler :) Yeah, I think there's something a bit funny going on. Like you say, either the docs, warning, method naming or implementation could probably...

Yeah, that could work ... Alternatively you could double up on backslashes in the ouput, something like, ``` js return JSON.stringify(stateTree).split('\\').join('\\\\'); ``` at https://github.com/acdlite/flummox/blob/master/src/Flux.js#L253

I think this either needs solving in the library itself, or in the docs. As it is the serialisation API is quite confusing, and doesn't work as advertised. I'd be...

Ah thanks. Yes, we're doing a similar workaround at the moment. It would be easier/better to have a single dedicated classname though, since complex selectors and pseudo-classes like `:first-of-type` etc....

I'm on macOS here.

This looks good, thanks! Will merge when I get a chance.

Cheers! I tracked down the change to that line and looks like it was introduced in this PR: https://github.com/jedrichards/rsyncwrapper/pull/25 To be honest, not sure which IO setup is more useful/idiomatic....

> Another rsync wrapper What the heck? All this time and I thought `rsyncwrapper` was the only Node rsync game in town! Plucky devil to go ahead and call the...

Yes I agree, there are a few pitfalls when using plugin context values this way. I got tripped up myself with this a few weeks ago, but it resolved itself...

Is this comparing the result between exporting from the (internal/cocoascript) JS API via the pasteboard vs. exporting natively/normally via the File > Export menu?