Mercurial > vim
view pixmaps/tb_maximize.xpm @ 13186:dc39ef257b60 v8.0.1467
patch 8.0.1467: libvterm doesn't handle illegal byte sequence correctly
commit https://github.com/vim/vim/commit/fef4ddd5eb8816a6607a624aa401bcfa71a63def
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Feb 4 14:49:57 2018 +0100
patch 8.0.1467: libvterm doesn't handle illegal byte sequence correctly
Problem: Libvterm doesn't handle illegal byte sequence correctly.
Solution: After the invalid code check if there is space to store another
character. Allocate one more character. (zhykzhykzhyk, closes
#2614, closes #2613)
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Sun, 04 Feb 2018 15:00:04 +0100 |
| parents | 3fc0f57ecb91 |
| children |
line wrap: on
line source
/* XPM */ static char * tb_maximize_xpm[] = { /* width height ncolors cpp [x_hot y_hot] */ "18 18 5 1 0 0", /* colors */ " s none m none c none", ". s topShadowColor m none c #DCDEE5", "X s iconColor1 m black c #000000", "o s iconColor2 m none c #FFFFFF", "O s bottomShadowColor m black c #5D6069", /* pixels */ " ", " .XXXXXXXXXXX ", " .X....X...oX ", " .X..oXXX..oXO ", " .X.oXXXXX.oXO ", " .X........oXO ", " .X........oXO ", " .X........oXO ", " .X........oXO ", " .X........oXO ", " .X........oXO ", " .X........oXO ", " .X..XXXXX.oXO ", " .X...XXX..oXO ", " .XooooXooooXO ", " .XXXXXXXXXXXO ", " OOOOOOOOOO ", " "};