Rasmus Thomsen

Ah, I can make full logs in a bit, those are from different runs indeed.

Alright, thank you very much for looking into this!

Heh, seems like GitHub tried to be too smart on this one?

Huh, I just tested this again with `gxi-linecache` changed a bit to work with xrl's `Update`s and now I have the same bug. I suppose this is something in gxi...

Alright, I think I've figured it out. I did a bit of debugging with gxi v0.8.1, the last release before I've switched to xrl. First I serialized a `Value` to...

See https://github.com/Cogitri/gxi/tree/gxi-linecache for a version of gxi that uses xrl for everything but the cache for debugging purposes :)

Ah, no, I still think we should go with xrl's LineCache due to xrl's version being faster, but while looking for what caused this I thought it'd be easiest to...

FWIW, Tau has used Xi as a lib for some time, simply sending the RPCs to another thread, like so: https://gitlab.gnome.org/World/Tau/blob/bb377b7fb8909c494cbe970da099a61ec7d47a78/src/gxi-peer/src/xi_thread.rs . I've talked with xi-editor upstream about making Xi...

Ah yes, Tau (gxi) did something similiar, I guess I might go for something similiar with xrl, but I'm not quite sure how to do it in an async manner...

So, the current status on this: I first tried implementing this into xi-editor by enabling it to use a Sender/Receiver pair instead of something that implements Read/Write, but that is...