Mercurial > vim
view runtime/compiler/splint.vim @ 33083:79b2eb83f2df v9.0.1827
patch 9.0.1827: xxd: no color support
Commit: https://github.com/vim/vim/commit/e2528ae11134cdf35c312754b124aba4963d8054
Author: Aapo Rantalainen <aapo.rantalainen@gmail.com>
Date: Thu Aug 31 17:58:13 2023 +0200
patch 9.0.1827: xxd: no color support
Problem: xxd: no color support
Solution: Add color support using xxd -R
Add some basic color support for xxd
The hex-value and value are both colored with the same color depending
on the hex-value, e.g.:
0x00 = white
0xff = blue
printable = green
non-printable = red
tabs and linebreaks = yellow
Each character needs 11 more bytes to contain color. (Same color in a
row could contain only one overhead but the logic how xxd creates colums
must be then changed.) Size of colored output is increased by factor of
~6. Also grepping the output will break when colors is used.
Flag for color is "-R", because less uses "-R".
Color uses parameters auto,always,never same as less and grep (among
others).
E.g.
xxd -R always $FILE | less -R
Add some screen-tests (that currently on work on linux) to verify the
feature works as expected.
closes: #12131
Signed-off-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: Aapo Rantalainen <aapo.rantalainen@gmail.com>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Thu, 31 Aug 2023 18:15:03 +0200 |
parents | 2704c4e3e20a |
children | e1df51f68736 |
line wrap: on
line source
" Vim compiler file " Compiler: splint/lclint (C source code checker) " Maintainer: Ralf Wildenhues <Ralf.Wildenhues@gmx.de> " Splint Home: http://www.splint.org/ " Last Change: 2019 Jul 23 " $Revision: 1.3 $ if exists("current_compiler") finish endif let current_compiler = "splint" if exists(":CompilerSet") != 2 " older Vim always used :setlocal command -nargs=* CompilerSet setlocal <args> endif let s:cpo_save = &cpo set cpo-=C " adapt this if you want to check more than one file at a time. " put command line options in .splintrc or ~/.splintrc CompilerSet makeprg=splint\ %:S " Note: when using the new array bounds checking flags: Each warning " usually has several lines and several references to source code mostly " within one or two lines (see sample warning below). The easiest way " not to mess up file name detection and not to jump to all positions is " to add something like " -linelen 500 +boundscompacterrormessages " to your .splintrc and 'set cmdheight=4' or more. " TODO: reliable way to distinguish file names and constraints. " " sample warning (generic): " "foo.c:1006:12: Clauses exit with var referencing local storage in one " case, fresh storage in other case " foo.c:1003:2: Fresh storage var allocated " " sample warning (bounds checking): " "bounds.c: (in function updateEnv) "bounds.c:10:5: Possible out-of-bounds store: " strcpy(str, tmp) " Unable to resolve constraint: " requires maxSet(str @ bounds.c:10:13) >= maxRead(getenv("MYENV") @ " bounds.c:6:9) " needed to satisfy precondition: " requires maxSet(str @ bounds.c:10:13) >= maxRead(tmp @ bounds.c:10:18) " derived from strcpy precondition: requires maxSet(<parameter 1>) >= " maxRead(<parameter 2>) " A memory write may write to an address beyond the allocated buffer. (Use " -boundswrite to inhibit warning) CompilerSet errorformat=%OLCLint*m, \%OSplint*m, \%f(%l\\,%c):\ %m, \%*[\ ]%f:%l:%c:\ %m, \%*[\ ]%f:%l:\ %m, \%*[^\"]\"%f\"%*\\D%l:\ %m, \\"%f\"%*\\D%l:\ %m, \%A%f:%l:%c:\ %m, \%A%f:%l:%m, \\"%f\"\\, \\ line\ %l%*\\D%c%*[^\ ]\ %m, \%D%*\\a[%*\\d]:\ Entering\ directory\ `%f', \%X%*\\a[%*\\d]:\ Leaving\ directory\ `%f', \%DMaking\ %*\\a\ in\ %f, \%C\ %#%m let &cpo = s:cpo_save unlet s:cpo_save