Open paulenit opened 2 years ago
I can confirm the bug as described. The empty new-line before the metadata header works as a workaround. Thought, this disables syntax-highligting.
A check to determine the pandoc flavoured markdown would be appreciated.
BOF
---
yaml
---
markdown
EOF
I can also confirm this issue, and I can offer another workaround: Putting the language string into quotes also helps.
Same bug on Ventura, thanks !
Describe the bug I tried to spell check a markdown document (in Pandoc's markdown flavor) but LTeX did not mark any errors despite them present. The document contained a YAML header (delimited by
---
) with thelang: en_US
value.The issue disappears when:
lang
tag is removed, orlang
value is changed fromen_US
toen-US
orde-DE
, a valid LTeX language identifier. This appears to only work when there is no other YAML tag after thelang
tag.The LTeX server log leads me to believe that LTeX is trying to use the language defined by the
lang
tag instead of the one set in the VSCode settings but fails at that consequently skipping the entire document.I might have overlooked the ability for LTeX to assert the language to check for from the document contents because when setting
lang: de-DE
LTeX flags non-German words as errors. So this YAML attribute clearly gets read by LTeX. However, in this case this should in my opinion not be fixable by inserting a blank line before the YAML block...Steps to reproduce Steps to reproduce the behavior:
Install latest version of VSCode and LTeX, paste the sample document and start a check
Expected behavior Spell checking.
Sample document If the bug occurs for a specific document (e.g. LaTeX), please paste it here. If your document is very long or confidential, please create and attach a smaller example for which the bug still occurs so that we can reproduce it.
LTeX configuration Please paste all configuration settings starting with
ltex.
from yoursettings.json
. You can help us by temporarily removing some irrelevant settings from yoursettings.json
and see if the bug still occurs."LTeX Language Server" log file First, reproduce the bug. Then, go to
View
→Output
and selectLTeX Language Server
in the drop-down list. Paste this log here:"LTeX Language Client" log file First, set the
ltex.trace.server
setting in yoursettings.json
to"verbose"
. Then, reload the VS Code window and reproduce the bug. Go toView
→Output
and selectLTeX Language Client
in the drop-down list. Paste this log here (note: it will contain your checked document):Version information List here the version information of the relevant software.
Additional context/information You can add any other context or information about the problem here.