Skip to content
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

TODO 3) get rid of terminfo cruft #10

Open
rofl0r opened this issue Mar 16, 2016 · 2 comments
Open

TODO 3) get rid of terminfo cruft #10

rofl0r opened this issue Mar 16, 2016 · 2 comments

Comments

@rofl0r
Copy link
Member

rofl0r commented Mar 16, 2016

the terminfo db is filled with a ton of junk; terminals that are unlikely to be ever encountered should be nuked from the list.

rather than starting to remove junk, the alternative is to do it the other way round:
start from zero and add the few terminals that are somewhat likely to be still in use in modern systems.

@oliverkwebb
Copy link

Bringing up this issue again, and yeah. No one is running a vt100 or apple 2 today, but terminfo has support for them. It's a cool historical relic I guess.

This is a question of What are the target systems of this project? What is the assumed environment? And what can be done with the subset of features from the projects target environments? Depending on what environment the project is focusing on, there might not even be a need for terminfo since ANSI + linux console_codes(4) could cover all the features needed to
run a fully functional ncurses on all used terminals.

I want to strip legacy code and terminfo junk out. But I don't know the bounds or the target systems of this project.

@rofl0r
Copy link
Member Author

rofl0r commented Sep 20, 2024

it should support all terminal emulators currently in use on major platforms (including the BSDs), but also keep working on a real serial connection. so i suppose vt100 should be kept as a backup. however i've somewhat revised my stance on this issue, since the few times i had to mess with the terminfo db were anything but pleasant. it's full of tricks only absolute experts can understand, even updating to the version shipped with ncurses caused hard-to-fix regressions. cleaning this stuff up to a reasonable minimum while everything keeps working is probably a herculean task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants