Show token locations on highlighting errors#14509
Conversation
971fdd7 to
9cc1786
Compare
|
A json/csv/yaml log of (path, line, char, error) would probably also help with tools that update docs and currently have to use these regexes in |
9cc1786 to
69bbc08
Compare
|
|
I don't think you need to regen the messages? I think it's done automatically (or maybe not anymore?) |
|
The translation files are handled in a separate process (semi-automatic, as it requires a manual merge). This is what the contributing guide says:
|
69bbc08 to
40ab948
Compare
…lder because the LaTeX builder tracks the source line number of the error Co-authored-by: Copilot <copilot@github.com>
40ab948 to
f609722
Compare
|
My mistake. I've rebased and removed the commit that attempted to add the translations. Attached: |
Purpose
Show token locations on highlighting errors, in order to make it easy to Ctrl-Click path:lineno references
(in order to find obscure issues with unbalanced appostrophes in comments in bash syntax-highligted docs)
This adds to the one line error message regex.
I've tried to update the translation files too. As noted on that commit, I've attempted to auto-updated the translation files with the model. Please do correct as necessary.
References
AI Disclosure