That is a strange error, because parse_cs_f_keys() is far away from line 7753 and does not contain anything alignment specific.
With the help of chatgpt I narrowed this down to the use of the ansi_table. If this is true, does it compile, if you disable the terminal (e.g. ./configure --disable-terminal)? If yes, can you please try the following patch:
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I am still getting the same error with --disable-terminal .
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
So if you remove the whole block here:
https://github.com/vim/vim/blob/aa9862a5b0e68581b07197f9c21b1441ab62a290/src/term.c#L7602-L7704
It still fails? Well, then can you bisect which patch causes the failure?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
It was still failing.
I have verified which version is the latest one that compiles without errors. It is 9.1.1735.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
So patch 9.1.1736 causes this which adds the parse_csi_f_keys() function. But I don't understand the error message, so not sure how to fix it.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Have you tried a different compiler?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Oh and just a wild guess, does this help?
diff --git a/src/term.c b/src/term.c index 4c365b19b..c317ca601 100644 --- a/src/term.c +++ b/src/term.c @@ -5362,7 +5362,7 @@ put_key_modifiers_in_typebuf( static int parse_csi_f_keys(int arg) { - char_u key_name[2] = ""; + char_u key_name[2] = { 0, 0 }; switch (arg) {
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Yes, this fixes it!
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()