-
-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any plans to support netbsd-curses? #578
Comments
What are you using toxic on that a 4 MiB binary is too large? |
Rather, it is not so much a space constraint than not having to require an external terminfo db as netbsd-curses has a (customizeable) built-in db for a closer-to-true-portable solution if toxic is built statically. Unrelated, but I needed to add -lsodium to LDFLAGS to build a static toxic (against both glibc and musl) on Debian, This was with pkg-config installed. |
There are no plans to support netbsd-curses, but I'm open to reviewing pull requests.
That shouldn't be necessary. Maybe @nurupo can chime in? |
I found it easier to invoke pkg-config with the --static flag instead of patching LDFLAGS directly. If you don't pass --static to it, it gives you output for shared/dynamic linking. toxic/script/build-minimal-static-toxic.sh Line 204 in 768617a
|
Terminfo and curses was designed to provide compatibility between 1970s-1980s hardware serial 'dumb' terminals, which used different commandsets to do common screen-manipulation things, like move cursor, erase line, etc. There is no reason to use ncurses anymore, now that nobody is using anything but an ANSI-compatible virtual terminal. Just issue ansi codes directly for cursor positioning, clear screen, erase line, set color. |
If you want to do this in a fork I'll gladly look it over |
I really like this client. If i can get my brain together enough to learn the code I'll see what can be done for incremental de-cursing. |
@clort81 How's it going? |
Static ncurses alone more than doubles the size of the binary. netbsd-curses might be a solution.
The text was updated successfully, but these errors were encountered: