Aaron Janse

That's a good idea. Unless there are any objections, I'll include that in `v1.0`

Partially fixed by #91. Boot panics should™ now be a thing of the past.

I can no longer reproduce this on master. Is this still an issue?

Resize issues are no longer fatal (https://github.com/aaronjanse/3mux/commit/f5dfdad1b66836c426e422e61d66a276bd41a68e) but I'm keeping this issue open until I can fix the underlying problem. Better logging is tracked at https://github.com/aaronjanse/3mux/issues/39

Absolutely! I plan on refactoring 3mux this week after receiving some helpful bug reports. I'll use that as an opportunity to make vterm usable on its own. For the foreseeable...

Does this sound good for a rough idea for a vterm API? - rune channel for input - interface for rendering output (color, set char at position, etc)

I've already got you covered :wink: https://github.com/aaronjanse/3mux/blob/438943668efbb16b479eea1867a28bb9f80909f6/vterm/stdout.go#L30

A not-yet-stable `vterm` package is available in `v0.3.0`. See `fuzz/main.go` for example usage.

Yep, this is an known issue, and I need to document it. The cause is that 3mux cannot control the selection of the terminal emulator. It could possibly use something...

Thank you for the fantastic bug report @mogenson! We've merged a few PRs to fix 3mux rendering issues that are obvious in Kakoune: - #110 (we didn't support the code...