Mercurial > vim
view runtime/syntax/bdf.vim @ 33674:021e5bb88513 v9.0.2074
patch 9.0.2074: Completion menu may be wrong
Commit: https://github.com/vim/vim/commit/daef8c74375141974d61b85199b383017644978c
Author: Christian Brabandt <cb@256bit.org>
Date: Fri Oct 27 19:16:26 2023 +0200
patch 9.0.2074: Completion menu may be wrong
Problem: Completion menu may be wrong
Solution: Check for the original direction of the completion menu,
add more tests, make it work with 'noselect'
completion: move in right direction when filling completion_info()
When moving through the insert completion menu and switching directions,
we need to make sure we start at the correct position in the list and
move correctly forward/backwards through it, so that we do not skip
entries and the selected item points to the correct entry in the list
of completion entries generated by the completion_info() function.
The general case is this:
1) CTRL-X CTRL-N, we will traverse the list starting from
compl_first_match and then go forwards (using the cp->next pointer)
through the list (skipping the very first entry, which has the
CP_ORIGINAL_TEXT flag set (since that is the empty/non-selected entry
2) CTRL-X CTRL-P, we will traverse the list starting from
compl_first_match (which now points to the last entry). The previous
entry will have the CP_ORIGINAL_TEXT flag set, so we need to start
traversing the list from the second prev pointer.
There are in fact 2 special cases after starting the completion menu
with CTRL-X:
3) CTRL-N and then going backwards by pressing CTRL-P again.
compl_first_match will point to the same entry as in step 1 above,
but since compl_dir_foward() has been switched by pressing CTRL-P
to backwards we need to pretend to be in still in case 1 and still
traverse the list in forward direction using the cp_next pointer
4) CTRL-P and then going forwards by pressing CTRL-N again.
compl_first_match will point to the same entry as in step 2 above,
but since compl_dir_foward() has been switched by pressing CTRL-N
to forwards we need to pretend to be in still in case 2 and still
traverse the list in backward direction using the cp_prev pointer
For the 'noselect' case however, this is slightly different again. When
going backwards, we only need to go one cp_prev pointer back. And
resting of the direction works again slightly different. So we need to
take the noselect option into account when deciding in which direction
to iterate through the list of matches.
related: #13402
related: #12971
closes: #13408
Signed-off-by: Christian Brabandt <cb@256bit.org>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Fri, 27 Oct 2023 19:30:05 +0200 |
parents | 1218c5353e2b |
children |
line wrap: on
line source
" Vim syntax file " Language: BDF font definition " Previous Maintainer: Nikolai Weibull <now@bitwi.se> " Latest Revision: 2006-04-19 if exists("b:current_syntax") finish endif let s:cpo_save = &cpo set cpo&vim syn region bdfFontDefinition transparent matchgroup=bdfKeyword \ start='^STARTFONT\>' end='^ENDFONT\>' \ contains=bdfComment,bdfFont,bdfSize, \ bdfBoundingBox,bdfProperties,bdfChars,bdfChar syn match bdfNumber contained display \ '\<\%(\x\+\|[+-]\=\d\+\%(\.\d\+\)*\)' syn keyword bdfTodo contained FIXME TODO XXX NOTE syn region bdfComment contained start='^COMMENT\>' end='$' \ contains=bdfTodo,@Spell syn region bdfFont contained matchgroup=bdfKeyword \ start='^FONT\>' end='$' syn region bdfSize contained transparent matchgroup=bdfKeyword \ start='^SIZE\>' end='$' contains=bdfNumber syn region bdfBoundingBox contained transparent matchgroup=bdfKeyword \ start='^FONTBOUNDINGBOX' end='$' \ contains=bdfNumber syn region bdfProperties contained transparent matchgroup=bdfKeyword \ start='^STARTPROPERTIES' end='^ENDPROPERTIES' \ contains=bdfNumber,bdfString,bdfProperty, \ bdfXProperty syn keyword bdfProperty contained FONT_ASCENT FONT_DESCENT DEFAULT_CHAR syn match bdfProperty contained '^\S\+' syn keyword bdfXProperty contained FONT_ASCENT FONT_DESCENT DEFAULT_CHAR \ FONTNAME_REGISTRY FOUNDRY FAMILY_NAME \ WEIGHT_NAME SLANT SETWIDTH_NAME PIXEL_SIZE \ POINT_SIZE RESOLUTION_X RESOLUTION_Y SPACING \ CHARSET_REGISTRY CHARSET_ENCODING COPYRIGHT \ ADD_STYLE_NAME WEIGHT RESOLUTION X_HEIGHT \ QUAD_WIDTH FONT AVERAGE_WIDTH syn region bdfString contained start=+"+ skip=+""+ end=+"+ syn region bdfChars contained display transparent \ matchgroup=bdfKeyword start='^CHARS' end='$' \ contains=bdfNumber syn region bdfChar transparent matchgroup=bdfKeyword \ start='^STARTCHAR' end='^ENDCHAR' \ contains=bdfEncoding,bdfWidth,bdfAttributes, \ bdfBitmap syn region bdfEncoding contained transparent matchgroup=bdfKeyword \ start='^ENCODING' end='$' contains=bdfNumber syn region bdfWidth contained transparent matchgroup=bdfKeyword \ start='^SWIDTH\|DWIDTH\|BBX' end='$' \ contains=bdfNumber syn region bdfAttributes contained transparent matchgroup=bdfKeyword \ start='^ATTRIBUTES' end='$' syn keyword bdfBitmap contained BITMAP if exists("bdf_minlines") let b:bdf_minlines = bdf_minlines else let b:bdf_minlines = 30 endif exec "syn sync ccomment bdfChar minlines=" . b:bdf_minlines hi def link bdfKeyword Keyword hi def link bdfNumber Number hi def link bdfTodo Todo hi def link bdfComment Comment hi def link bdfFont String hi def link bdfProperty Identifier hi def link bdfXProperty Identifier hi def link bdfString String hi def link bdfChars Keyword hi def link bdfBitmap Keyword let b:current_syntax = "bdf" let &cpo = s:cpo_save unlet s:cpo_save