PDCurses VS notty

The latest version can be found at: https://pdcurses.org/

I use GDB with openocd on ubuntu system to debug a Samd51 MCU using jlink. it's working good until when I lay next and look at the source code in graphical terminal, so if I scroll in TUI source code, GDB crashed and start printing in weird way(not sure if it's GDB It's might be the ubuntu terminal not liking it). So I decided to use it on windows with the jlink GDB server app, But the issue no is I can't use the TUI interface in windows terminal, and it says not supported, while some people on the internet talking about a missing curses lib. from pdcurses.org on windows that's why not working. any one having any idea on how to make the TUI works?

However, I now experimented a litte with the PDCurses implementation in Windows 11, and found that

I'm not sure of what's good or bad of the various variants but quick googling found (https://github.com/wmcbrine/PDCurses).

Since ncurses doesn't support Windows, you need PDCurses instead. After extracting the source tarball, cd into wincon/ and run make, which produces pdcurses.a static library. You'll need that library and curses.h from the project root.

nnn uses the ncurses library. Someone has to compile it with PDCurses to work natively in cmd: https://pdcurses.org/

On Windows you might need to use a shim layer (https://pdcurses.org/). However that actually creates an SDL based window and prints characters there.

Declarative terminal graphics for OCaml

As some can guess, the architecture was heavily inspired by Elm and Elmish parent-child patterns. Notty - is a cool library, which is a perfect choice for a simple terminal draw. But keep in mind, that you will be responsible for focus management and isolation of all event handlings. Sqlite3-OCaml - is totally imperative library, because it is just bindings on C library. But you get all the essential functionality with which you can build yourself the needed level of abstraction.