You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a Vim issue with handling of multi-byte characters, if Vim's errorformat is used to parse mult-line messages. See here for the bug description.
This causes problems with Vim plugins, e.g. the compiler vlty for vimtex, if the LaTeX text contains many multi-byte characters, as in Russian texts with cyrillic letters. See here for an example.
Even if the Vim issue is fixed, it will take some time for the fix to be incorporated into Linux distributions. We therefore should provide a single-line format for option --output, for instance
--output sl-1: include file name, line, column, LT'serror message text
--output sl-2: as sl-1, but append LT's replacement suggestions
This option should be used in editors/vlty.py and editors/ltyc.py.
The text was updated successfully, but these errors were encountered:
There seems to be a Vim issue with handling of multi-byte characters, if Vim's
errorformat
is used to parse mult-line messages. See here for the bug description.This causes problems with Vim plugins, e.g. the compiler vlty for vimtex, if the LaTeX text contains many multi-byte characters, as in Russian texts with cyrillic letters. See here for an example.
Even if the Vim issue is fixed, it will take some time for the fix to be incorporated into Linux distributions. We therefore should provide a single-line format for option --output, for instance
--output sl-1
: include file name, line, column, LT'serror message text--output sl-2
: as sl-1, but append LT's replacement suggestionsThis option should be used in editors/vlty.py and editors/ltyc.py.
The text was updated successfully, but these errors were encountered: