Open joseluis opened 1 year ago
ick! good find. i think i saw something like this before, but am uncertain. let me look into it.
do your kitty problems happen with the last released notcurses, prior to the merging of #2695 ?
btw good to hear from you buddy =] i remain swamped working on satellites, but i'm expecting to be able to descend back upon this project come summer.
do your kitty problems happen with the last released notcurses, prior to the merging of #2695 ?
mmm I'm not 100% sure, I hadn't recompiled notcurses in a while, but I'm sure it was v3.0.9, I just updated and recompiled and I see no difference. I also tested with kitty 0.26 and 0.27 and it's the same.
btw good to hear from you buddy =] i remain swamped working on satellites, but i'm expecting to be able to descend back upon this project come summer.
good to hear from you too pal =) I'm finally trying to use notcurses to build things, so I'll maybe find some more before summer hehe
In case it's helpful: ctrl-z
and fg
seem to work correctly if NCOPTION_DRAIN_INPUT
is used.
For example, poc/gradients
can be suspended and resumed without any problem.
After suspending an app with
ctrl-z
and bringing it up to the foreground withfg
, the events are not processed as they were before, but the inputs are echoed to the terminal and not received until pressing enter. That looks as if we'd had abandoned the raw mode and entered the default terminal mode.It can be replicated with
notcurses-input
on every terminal, but in kitty is even worse and nothing seems to work anymore after suspending a notcurses app, which doesn't happen with other apps.