Hacker News new | past | comments | ask | show | jobs | submit login

I really dislike that they re-used the TERM value from xterm instead of getting their own merged into terminfo. And then not documenting which sequences are actually supported and which aren't.



You would be surprised how much software is built exclusively for TERM=xterm or TERM=xterm-*.


I'm aware and i think its not okay. Its incorrect software.

And yes, that difference is significant because the F-keys, Ins, End and companions won't work.


You're getting downvoted but you're not wrong. Using TERM=xterm-* should be deprecated, and in this case in particular that likely means stepping on some toes.


It's like the user agent string in browsers. Using that instead of checking for feature availability directly is always going to end up in a mess like this over time. Heck, there wasn't a Windows 9 because of how much software would break because they had `if (osversion.startswith("9"))` check to decide if it needs to act in pre-XP mode, long after XP itself was EOL. Most people aren't willing to give up functional workflows on principle alone. "stepping on some toes" massively understates the impact.


Which is exactly the root cause of terminal weirdness.

Instead of a standard, we have mountains of terminfo entries which are mostly slight xterm variants and ancient hardware


Sounds like the user agent string in web browsers.


They have their own, and it's documented.

https://invisible-island.net/ncurses/terminfo.src.html#tic-m...

Surely you can imagine that it takes years or more to get people to update though, so switching to a new entry right away could make for a bad user experience.


That's not made by them and not supported by upstream, see full thread: https://lists.gnu.org/archive/html/bug-ncurses/2019-08/msg00...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: