view pixmaps/error.xpm @ 33631:9f55ea4702b1

matchparen: do not use hard-coded match id (#13393) Commit: https://github.com/vim/vim/commit/d3e277f279ed628809eb6857ea3ebcfca566ca2a Author: Christian Brabandt <cb@256bit.org> Date: Sat Oct 21 11:06:50 2023 +0200 matchparen: do not use hard-coded match id (https://github.com/vim/vim/issues/13393) * matchparen: do not use hard-coded match id Instead of using the hard-coded match id 3, which may also be used by other plugins, let the matchparen plugin use whatever ids are automatically returned when calling matchaddpos(). For backwards-compatibility, keep the `:3match` call, which will still use the hard-coded id 3 (as mentioned in :h :3match). closes: #13381 Signed-off-by: Christian Brabandt <cb@256bit.org>
author Christian Brabandt <cb@256bit.org>
date Sat, 21 Oct 2023 11:15:05 +0200
parents 3fc0f57ecb91
children
line wrap: on
line source

/* XPM */
static char * error_xpm[] = {
/* width height ncolors cpp [x_hot y_hot] */
"34 34 4 1 0 0",
/* colors */
" 	s none	m none	c none",
".	s iconColor3	m black	c #FF0000",
"X	s bottomShadowColor	m black	c #5D6069",
"o	s iconColor2	m white	c #FFFFFF",
/* pixels */
"                                  ",
"            ........              ",
"          ............            ",
"        ................          ",
"       ..................         ",
"      ....................X       ",
"     ......................X      ",
"    ........................X     ",
"   .......o..........o.......X    ",
"   ......ooo........ooo......X    ",
"  ......ooooo......ooooo......X   ",
"  .......ooooo....ooooo.......X   ",
" .........ooooo..ooooo.........X  ",
" ..........oooooooooo..........X  ",
" ...........oooooooo...........XX ",
" ............oooooo............XX ",
" ............oooooo............XX ",
" ...........oooooooo...........XX ",
" ..........oooooooooo..........XX ",
" .........ooooo..ooooo.........XX ",
"  .......ooooo....ooooo.......XX  ",
"  ......ooooo......ooooo......XX  ",
"   ......ooo........ooo......XXX  ",
"   .......o..........o.......XX   ",
"    ........................XXX   ",
"     ......................XXX    ",
"     X....................XXX     ",
"      X..................XXX      ",
"       X................XXX       ",
"        XX............XXXX        ",
"          XX........XXXXX         ",
"            XXXXXXXXXXX           ",
"              XXXXXXX             ",
"                                  "};