Michael Davis

Ah I think I know what the issue is. Could you try setting TCP nodelay and see how that fares? ```elixir Spear.Connection.start_link(connection_string: "esdb://localhost:2113?tls=false", mint_opts: [transport_opts: [nodelay: true]]) ``` We're sending...

See https://github.com/helix-editor/helix/pull/11080

Ah I think `Spear.Reading.Stream.unfold_chunk/1` is `spec`'d incorrectly: it should be `tuple()` instead of `struct()` since each message is decoded by `gpb` as a record

I think it would be useful to have a way to select the next pairing of a certain kind (or of any kind), but I believe this should belong under...

I'm also thinking that we would drop the i/a part and use "around" like the other `goto_next_` commands, so it would be `]{` for example rather than `]i{`. The jump...

I agree, nuanced behavior like that can be confusing especially when you're working with multiple selections. I'd like to avoid the `i` if we can to avoid making `]` too...

I squashed the `fold/3` change into the main change (last commit) and added a small blurb to that commit message about `fold/3` :+1:

I wrote that function in crossterm (https://github.com/crossterm-rs/crossterm/pull/732). I'm a bit confused by https://sw.kovidgoyal.net/kitty/keyboard-protocol/#detection-of-support-for-this-protocol now: > An application can query the terminal for support of this protocol by sending the escape...

I misread the above post, thanks for clarifying! I thought you were saying that `CSI ? u` sent before any push requests would show the supported flags but I believe...

Adding a function to crossterm to query the currently active flags should be a really small change, I don't mind sending a PR to crossterm for that. (Edit: https://github.com/crossterm-rs/crossterm/pull/958) After...