view runtime/vim16x16.xpm @ 34257:8a91d18f1789 v9.1.0069

patch 9.1.0069: ScreenLines may not be correctly initialized, causing hang Commit: https://github.com/vim/vim/commit/fd472655a93fd539c731c8daf3adc4e65ddce341 Author: Olaf Seibert <rhialto@falu.nl> Date: Thu Feb 1 21:11:16 2024 +0100 patch 9.1.0069: ScreenLines may not be correctly initialized, causing hang Problem: ScreenLines may not be correctly initialized, causing hang (Olaf Seibert, after 9.0.0220) Solution: always initialize ScreneLines when allocating a screen (Olaf Seibert) ScreenLines and related structures could be left uninitialized causing a screen update to run into an infinite loop when using latin1 encoding. Partly caused because by patch 9.0.0220, which makes mb_ptr2len return zero for NUL related: #12671 closes: #13946 Signed-off-by: Olaf Seibert <rhialto@falu.nl> Signed-off-by: Christian Brabandt <cb@256bit.org>
author Christian Brabandt <cb@256bit.org>
date Thu, 01 Feb 2024 21:30:02 +0100
parents 3fc0f57ecb91
children 8f04cf65ecff
line wrap: on
line source

/* XPM */
static char * vim16x16[] = {
"16 16 8 1",
" 	c None",
".	c #000000",
"+	c #000080",
"@	c #008000",
"#	c #00FF00",
"$	c #808080",
"%	c #C0C0C0",
"&	c #FFFFFF",
"  .....#. ....  ",
" .&&&&&.@.&&&&. ",
" .%%%%%$..%%%%$.",
"  .%%%$.@.&%%$. ",
"  .%%%$..&%%$.  ",
"  .%%%$.&%%$..  ",
" #.%%%$&%%$.@@. ",
"#@.%%%&%%$.@@@@.",
".@.%%%%%..@@@@+ ",
" ..%%%%.%...@.  ",
"  .%%%%...%%.%. ",
"  .%%%.%%.%%%%%.",
"  .%%$..%.%.%.%.",
"  .%$.@.%.%.%.%.",
"   .. .%%.%.%.%.",
"       .. . . . "};