view pixmaps/tb_ctags.xpm @ 32724:83111104fb89

Update the vimscript code for restoring cursor position Commit: https://github.com/vim/vim/commit/81b8bf5b4a33552c610dc2ea743ac2698a16aef7 Author: Dragan Simic' via vim_dev <vim_dev@googlegroups.com> Date: Wed Aug 9 17:23:58 2023 +0200 Update the vimscript code for restoring cursor position Using xxd(1) to filter and edit binary files causes the input files to have dual nature, so to speak, which effectively makes restoring the cursor position broken. Fix that by ignoring the "xxd" file type in the code that restores the cursor position. Interactive rebasing in git causes files to be edited in vim, which, similarly to commit messages, are rarely the same as the last one edited. Thus, also add "gitrebase" to the list of file types for which the cursor position isn't restored. While there, refactor the code a bit to possibly save a few CPU cycles and to keep the line lengths in check, and use the long form of the commands and variables, to make the code slightly more consistent and more understandable to newcomers. Update the relevant comments in the code and the associated parts of the documentation, to keep them in sync with the updated code. Remove some redundant trailing whitespace as well, as spotted.
author Christian Brabandt <cb@256bit.org>
date Thu, 10 Aug 2023 07:00:04 +0200
parents 3fc0f57ecb91
children
line wrap: on
line source

/* XPM */
static char * tb_ctags_xpm[] = {
/* width height ncolors cpp [x_hot y_hot] */
"18 18 7 1 0 0",
/* colors */
" 	s none	m none	c none",
".	s iconColor1	m black	c #000000",
"X	s iconColor2	m none	c #FFFFFF",
"o	s bottomShadowColor	m black	c #5D6069",
"O	m black	c #888800",
"+	s topShadowColor	m none	c #DCDEE5",
"@	s iconColor6	m none	c #FFFF00",
/* pixels */
"     .. .....     ",
"    .XX.XXXXX.    ",
"    .XXXXXXXXX.   ",
"    .XX.XXXX..X.  ",
"     .. ....o ..  ",
"   OO++O+...+O+.+ ",
"  Oo@@@@@...o@@@.o",
" Oo@@@@@@...o@@@.o",
"Oo@+o+@@@...o@@@.o",
"O@@o.o@@@...o@@@.o",
"o@@+o+@@@...o@@@.o",
"o.@@@@@@@...o@@@.o",
" o.@@@@@@...o@@@.o",
"  o.........o....o",
"   oooooo...oooooo",
"         ...o     ",
"         ...o     ",
"          ooo     "};