mirror of
https://github.com/vim/vim.git
synced 2026-02-05 11:34:36 +01:00
0fde6aebdd
As reported in #16559, bytes of a multibyte character may be written as separate U+FFFD characters in a ":terminal" window on a busy machine. The testing facilities currently offer an optional filtering step to be carried out between reading and comparing the contents of two screendump files for each such file. This filtering has been resorted to (#14767 and #16560) in an attempt to unconditionally replace known non-Latin-1 characters with an arbitrary substitute ASCII character and avoid this rendering mishap leading to syntax tests failures. However, it has been overlooked at the time that metadata description (in shorthand) to follow spurious U+FFFD characters may be *distinct* and make the remainder of such a line, ASCII characters and whatnot, also unequal between compared screendump files. While it is straightforward to adapt current filter files to ignore the line characters after the leftmost U+FFFD, > It is challenging and error-prone to keep up to date filter > files because moving around examples in source files will > likely make redundant some previously required filter files > and, at the same time, it may require creating new filter > files for the same source file; substituting one multibyte > character for another multibyte character will also demand > a coordinated change for filter files. Besides, unconditionally dropping arbitrary parts of a line is rather too blunt an instrument. An alternative approach is to not use the supported filtering for this purpose; let a syntax test pass or fail initially; then *if* the same failure is imminent, drop the leftmost U+FFFD and the rest of the previously seen line (repeating it for all previously seen unequal lines) before another round of file contents comparing. The obvious disadvantage with this filtering, unconditional and otherwise, is that if there are consistent failures for _other reasons_ and the unequal parts happen to be after U+FFFDs, then spurious test passing can happen when stars align for _a particular test runner_. Hence syntax test authors should strive to write as little significant text after multibyte characters as syntactically permissible, write multibyte characters closer to EOL in general, and make sure that their checked-in and published "*.dump" files do not have any U+FFFDs. It is also practical to refrain from attempting screendump generation if U+FFFDs can already be discovered, and instead try re-running from scratch the syntax test in hand, while accepting other recently generated screendumps without going through with new rounds of verification. Reference: https://github.com/vim/vim/pull/16470#issuecomment-2599848525 closes: #17704 Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
This directory contains Vim scripts for syntax highlighting. These scripts are not for a language, but are used by Vim itself: syntax.vim Used for the ":syntax on" command. Uses synload.vim. manual.vim Used for the ":syntax manual" command. Uses synload.vim. synload.vim Contains autocommands to load a language file when a certain file name (extension) is used. And sets up the Syntax menu for the GUI. nosyntax.vim Used for the ":syntax off" command. Undo the loading of synload.vim. The "shared" directory contains generated files and what is used by more than one syntax. A few special files: 2html.vim Converts any highlighted file to HTML (GUI only). colortest.vim Check for color names and actual color on screen. hitest.vim View the current highlight settings. whitespace.vim View Tabs and Spaces. If you want to write a syntax file, read the docs at ":help usr_44.txt". If you make a new syntax file which would be useful for others, please send it to the vim-dev mailing list <vim-dev@vim.org>. Include instructions for detecting the file type for this language, by file name extension or by checking a few lines in the file. And please write the file in a portable way, see ":help 44.12". If you have remarks about an existing file, send them to the maintainer of that file. Only when you get no response send a message to the vim-dev mailing list: <vim-dev@vim.org>. If you are the maintainer of a syntax file and make improvements, send the new version to the vim-dev mailing list: <vim-dev@vim.org> For further info see ":help syntax" in Vim.