gregnis

BTW, I tried using -sEMULATE_FUNCTION_POINTER_CASTS=1, and it didn't help. In fact, it broke other grammars, so I reset it back.

I was going off https://en.wikipedia.org/wiki/INI_file, the Comments section. I do agree with you about following GetPrivateProfileString as a spec, and if you do that, the current behavior is almost correct....

> OTOH, gitconfig appears to support inline comments, except when quoted in a string? I think this is the most reasonable thing to do, if possible,

I attached the failing file here (change .lua.txt to .lua) [common2.lua.txt](https://github.com/user-attachments/files/17446983/common2.lua.txt). And here's the tree: [tree.txt](https://github.com/user-attachments/files/17447004/tree.txt)

I don't know, not a Lua programmer. I can see though that VSCode highlights the file in question without any issues. 

So you are OK with the parser not recovering until over 100 lines after a "bad" line?

My point is that one of the main features of tree-sitter is its ability to recover from errors. That even bad syntax will not break the parser. It's hard to...