Mercurial > vim
view pixmaps/info.xpm @ 34584:2bedc8f066ff
runtime(syntax-tests): Support embeddable Vim configuration for syntax tests
Commit: https://github.com/vim/vim/commit/93edd254d5d809cfa85c87b4cedb8b649c999494
Author: Aliaksei Budavei <0x000c70@gmail.com>
Date: Tue Mar 5 22:34:36 2024 +0300
runtime(syntax-tests): Support embeddable Vim configuration for syntax tests
Currently, the very same syntax file for which a test can
be written is the only place where global variables can be
defined so that the file parts guarded with such variables
can be read during screen dump generation. This approach
would lead to littering the syntax file with test-related
queries.
Instead, we could borrow the idea of comment-based mechanism
for test setup from the indent test runner. With it, the
first 20 lines of each test file would be ALWAYS scanned in
search of the TEST_SETUP markers and, when found, the part
between the end of the marker and the end of the line would
be treated as a Vim Ex command.
Note that with these changes, runtime/defaults.vim is no
longer sourced for screen dump generation; however, some of
its functionality is reintroduced.
Further details can be found in the discussion thread at
https://github.com/vim/vim/discussions/14117.
related: #14215
Signed-off-by: Aliaksei Budavei <0x000c70@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Mon, 18 Mar 2024 19:45:02 +0100 |
| parents | 3fc0f57ecb91 |
| children |
line wrap: on
line source
/* XPM */ static char * info_xpm[] = { /* width height ncolors cpp [x_hot y_hot] */ "34 34 4 1 0 0", /* colors */ " s none m none c none", ". s bottomShadowColor m black c #5D6069", "X s iconColor2 m white c #FFFFFF", "o s iconColor1 m black c #000000", /* pixels */ " ", " ........ ", " ...XXXXXXXX... ", " ..XXXXXXXXXXXXXX.. ", " .XXXXXXXXXXXXXXXXXX. ", " .XXXXXXXXooooXXXXXXXXo ", " .XXXXXXXXooooooXXXXXXXXo ", " .XXXXXXXXXooooooXXXXXXXXXo ", " .XXXXXXXXXXXooooXXXXXXXXXXXo ", " .XXXXXXXXXXXXXXXXXXXXXXXXXXo. ", " .XXXXXXXXXXXXXXXXXXXXXXXXXXXXo. ", " .XXXXXXXXXXoooooooXXXXXXXXXXXo. ", " .XXXXXXXXXXXXoooooXXXXXXXXXXXo.. ", " .XXXXXXXXXXXXoooooXXXXXXXXXXXo.. ", " .XXXXXXXXXXXXoooooXXXXXXXXXXXo.. ", " .XXXXXXXXXXXXoooooXXXXXXXXXXXo.. ", " .XXXXXXXXXXXXoooooXXXXXXXXXXXo.. ", " .XXXXXXXXXXXoooooXXXXXXXXXXo... ", " .XXXXXXXXXXXoooooXXXXXXXXXXo... ", " .XXXXXXXXXXoooooXXXXXXXXXo... ", " oXXXXXXXoooooooooXXXXXXo.... ", " oXXXXXXXXXXXXXXXXXXXXo.... ", " oXXXXXXXXXXXXXXXXXXo.... ", " ooXXXXXXXXXXXXXXoo.... ", " .oooXXXXXXXXooo..... ", " ...oooXXXXo....... ", " ....oXXXo..... ", " .oXXXo.. ", " oXXo.. ", " oXo.. ", " oo.. ", " ... ", " .. ", " "};