view pixmaps/error.xpm @ 14057:be8fb2fd51fc v8.1.0046

patch 8.1.0046: loading a session file fails if 'winheight' is big commit https://github.com/vim/vim/commit/1c3c10492a291270fa89b3c8df11828792f927d3 Author: Bram Moolenaar <Bram@vim.org> Date: Tue Jun 12 16:49:30 2018 +0200 patch 8.1.0046: loading a session file fails if 'winheight' is big Problem: Loading a session file fails if 'winheight' is a big number. Solution: Set 'minwinheight' to zero at first. Don't give an error when setting 'minwinheight' while 'winheight' is a big number. Fix using vertical splits. Fix setting 'minwinwidth'. (closes #2970)
author Christian Brabandt <cb@256bit.org>
date Tue, 12 Jun 2018 17:00:07 +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             ",
"                                  "};