Jakub Okoński

Looks like it's all down to session serialization that runs on an interval. Once the session is saved at least once, quitting or `zellij kill-session` is going to preserve its...

I tried reproducing on `$ cargo run --example static --features=static_output,search` but it has different bugs: 1. backwards search `?` does not engage at all 2. previous result with `p` does...

I'm not familiar with crossterm and don't know if you've seen it already, but there's crossterm-rs/crossterm#778 already. It sounds like it may solve at least some of the issues identified...

That issue also leads to #141. I could try a full end to end test by integrating the latest `minus` into `jj` to see which issues remain (if any).

OK, testing on https://github.com/AMythicDev/minus/commit/43aa50d78a7fa1205fd7d37242d30ac0344461e8, they're not doubled anymore, but they: 1. Feel debounced/delayed - I think it tries to repaint after every character which can slow down perceived input 2....

This seems to work as expected, but I don't know enough to say if an extra type parameter affects the implicit search in practice (would it succeed in all cases...

> I don't know if you intend that the given First is always a singleton (unparameterized). That's right. In my real code, I generate a lot of types with scalameta...

Isn't it strange that a non-implicit definition infers all of this automatically? ```scala scala> def secondFromFirst[T](using first: First[T]) = new Second[T]: | | type AssociatedSecond = first.AssociatedFirst | def secondFromFirst...

I did figure it out now with refinement types and it's been working fine. Just bothers me a little that it's not the default and you need to be aware...

I keep running into this regularly and also discovered #20061 through googling. With `-language:experimental.modularity -source future`, this solves the problem cleanly: ```scala given [T](using tracked val first: First[T]): Second[T] with...