+1 -1

jj_tui/bin/main.ml

reviewed

··· 55 55 56 56 let start_ui () = 57 57 (*initialse the state*) 58 58 - let term = Notty_unix.Term.create () in 58 58 + let term = Notty_unix.Term.create ~mouse:false () in 59 59 Vars.term := Some term; 60 60 ui_loop ~quit:Vars.quit ~term (Jj_ui.mainUi ()); 61 61 Flock.terminate ()

+12

todo.md

reviewed

··· 6 6 - Inside my own program. 7 7 - I could make all components take an `keyList` record and let the caller override that. 8 8 - This option is more versitile because it allows one list to use say, arrows, and the other to use something like hjkl 9 9 + 9 10 ## Handling unusual key combos: 10 11 - Aparrently general ansi terminals don't properly distinguish many key combos. But kitty and newer protocols do. 11 12 - Maybe I could use this protocol within notty. 13 13 + 14 14 + 15 15 + ## Multithreaded/async support in picos. 16 16 + Currently if you set the timeout of nottui to 0 it will wait forever for input before it updates the ui. 17 17 + we need a way to interrupt the ui waiting if the internal state has changed. 18 18 + Basically the internal nottui loop should be: 19 19 + Wait on input/a lwd.var change. 20 20 + If there is a change, re-run 21 21 + - This allows for way less idle usage 22 22 + - This allows us to support selection 23 23 + - Currently we cannot select becasue the terminal is constatnly re-rendering, I could fix that now probably, but the picos change would also fix it