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

Are extended terminfo files being correctly parsed? #129

Open
mlabbe opened this issue Dec 5, 2019 · 2 comments
Open

Are extended terminfo files being correctly parsed? #129

mlabbe opened this issue Dec 5, 2019 · 2 comments

Comments

@mlabbe
Copy link

mlabbe commented Dec 5, 2019

Code contains #define TI_ALT_MAGIC 542, which is the alternative header for terminfo "extended storage format". This is ultimately used to correctly calculate the strings offset into the compiled terminfo database.

However, term(5) states that the alt magic is 0542, which is octal. TI_ALT_MAGIC should be set to (int)354, or prefixed with a zero.

I don't have any extended storage format terminfo files handy, but I am happy to test if you point me to where I can get some.

@nsf
Copy link
Owner

nsf commented Dec 5, 2019

See: nsf/termbox-go#185 (comment)

Yes indeed docs mention octal, but it's different in actual files. Weird.

@mlabbe
Copy link
Author

mlabbe commented Dec 5, 2019

Huh. Apparently it's been acknowledged by the manpage author. I went to report it upstream but it seems to be known.

https://lists.gnu.org/archive/html/bug-ncurses/2019-01/msg00031.html

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