Closed lwestfall closed 12 months ago
Hi @mike-lischke, I don't mean to be annoying or impatient by pinging you, but is there anything I can do or provide that might help lead to a solution? I'm wondering if these symptoms are related to some of the other more recent issues that have been posted.
FYI I just packaged the vsix locally after your recent changes (realizing you might have good reason to hold off on publishing a new release) and can confirm that 2.4.3 fixes all of my symptoms.
Ah excellent, thanks for the confirmation. Yes, I have yet to fix a number issues before I can release the next version and I don't want to do a release in haste.
I have a project that went on the backburner for several months. After returning to it in the last couple of days (and the extension updating to the latest release presumably) it appears that my split grammar isn't being properly generated. This was working perfectly fine when I last worked on it around 8 months ago.
My grammar files can be found here for repro: https://github.com/lwestfall/TeXpressions/tree/main/src/Grammars
I don't have any extension setting overrides, just the defaults apply.
Symptoms:
It appears that the top level grammar file (TeXpression.g4), when opened, generates parser and lexer files for TeXpression, but not its import (Logic.g4) or any of the other dependent grammar files. I can go into each grammar file manually and the files generate, but when I try to debug I get this error:
launch.json (can also be found in the above linked repo):
Output log when opening TeXpression.g4: