Mercurial > vim
view runtime/syntax/dylan.vim @ 34416:0a458b49e1e6 v9.1.0131
patch 9.1.0131: buffer-completion may not always find all matches
Commit: https://github.com/vim/vim/commit/0dc0bff000fd804c6b0778ccc4554a4e4c82c8c9
Author: Christian Brabandt <cb@256bit.org>
Date: Sat Feb 24 14:12:13 2024 +0100
patch 9.1.0131: buffer-completion may not always find all matches
Problem: buffer-completion code too complicated and does not always
find all matches (irisjae)
Solution: do not try to anchor pattern to beginning of line or
directory-separator, always return all matches
Note: we are considering the non-fuzzy buffer-matching here.
Currently, the buffer-completion code makes 2 attempts to match a
pattern against the list of available patterns. First try is to match
the pattern and anchor it to either the beginning of the file name or
at a directory-separator (// or \\).
When a match is found, Vim returns the matching buffers and does not try
to find a match anywhere within a buffer name. So if you have opened two
buffers like /tmp/Foobar.c and /tmp/MyFoobar.c using `:b Foo` will only
complete to the first filename, but not the second (the same happens
with `getcompletion('Foo', 'buffer')`).
It may make sense, that completion priorities buffer names at directory
boundaries, but it inconsistent, may cause confusion why a certain
buffer name is not completed when typing `:b Foo<C-D>` which returns
only a single file name and then pressing Enter (to switch to that
buffer), Vim will error with 'E93: More than one match for Foo').
Similar things may happen when wiping the /tmp/Foobar.c pattern and
afterwards the completion starts completing other buffers.
So let's simplify the code and always match the pattern anywhere in the
buffer name, do not try to favor matches at directory boundaries. This
is also simplifies the code a bit, we do not need to run over the list
of buffers several times, but only twice.
fixes #13894
closes: #14082
Signed-off-by: Christian Brabandt <cb@256bit.org>
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Sat, 24 Feb 2024 14:30:03 +0100 |
| parents | 46763b01cd9a |
| children |
line wrap: on
line source
" Vim syntax file " Language: Dylan " Authors: Justus Pendleton <justus@acm.org> " Brent A. Fulgham <bfulgham@debian.org> " Last Change: Fri Sep 29 13:45:55 PDT 2000 " " This syntax file is based on the Haskell, Perl, Scheme, and C " syntax files. " Part 1: Syntax definition " quit when a syntax file was already loaded if exists("b:current_syntax") finish endif syn case ignore setlocal lisp " Highlight special characters (those that have backslashes) differently syn match dylanSpecial display contained "\\\(x\x\+\|\o\{1,3}\|.\|$\)" " Keywords syn keyword dylanBlock afterwards begin block cleanup end syn keyword dylanClassMods abstract concrete primary inherited virtual syn keyword dylanException exception handler signal syn keyword dylanParamDefs method class function library macro interface syn keyword dylanSimpleDefs constant variable generic primary syn keyword dylanOther above below from by in instance local slot subclass then to syn keyword dylanConditional if when select case else elseif unless finally otherwise then syn keyword dylanRepeat begin for until while from to syn keyword dylanStatement define let syn keyword dylanImport use import export exclude rename create syn keyword dylanMiscMods open sealed domain singleton sideways inline functional " Matching rules for special forms syn match dylanOperator "\s[-!%&\*\+/=\?@\\^|~:]\+[-#!>%&:\*\+/=\?@\\^|~]*" syn match dylanOperator "\(\<[A-Z][a-zA-Z0-9_']*\.\)\=:[-!#$%&\*\+./=\?@\\^|~:]*" " Numbers syn match dylanNumber "\<[0-9]\+\>\|\<0[xX][0-9a-fA-F]\+\>\|\<0[oO][0-7]\+\>" syn match dylanNumber "\<[0-9]\+\.[0-9]\+\([eE][-+]\=[0-9]\+\)\=\>" " Booleans syn match dylanBoolean "#t\|#f" " Comments syn match dylanComment "//.*" syn region dylanComment start="/\*" end="\*/" " Strings syn region dylanString start=+"+ skip=+\\\\\|\\"+ end=+"+ contains=dySpecial syn match dylanCharacter "'[^\\]'" " Constants, classes, and variables syn match dylanConstant "$\<[a-zA-Z0-9\-]\+\>" syn match dylanClass "<\<[a-zA-Z0-9\-]\+\>>" syn match dylanVariable "\*\<[a-zA-Z0-9\-]\+\>\*" " Preconditions syn region dylanPrecondit start="^\s*#\s*\(if\>\|else\>\|endif\>\)" skip="\\$" end="$" " These appear at the top of files (usually). I like to highlight the whole line " so that the definition stands out. They should probably really be keywords, but they " don't generally appear in the middle of a line of code. syn region dylanHeader start="^[Mm]odule:" end="^$" " Define the default highlighting. " Only when an item doesn't have highlighting yet hi def link dylanBlock PreProc hi def link dylanBoolean Boolean hi def link dylanCharacter Character hi def link dylanClass Structure hi def link dylanClassMods StorageClass hi def link dylanComment Comment hi def link dylanConditional Conditional hi def link dylanConstant Constant hi def link dylanException Exception hi def link dylanHeader Macro hi def link dylanImport Include hi def link dylanLabel Label hi def link dylanMiscMods StorageClass hi def link dylanNumber Number hi def link dylanOther Keyword hi def link dylanOperator Operator hi def link dylanParamDefs Keyword hi def link dylanPrecondit PreCondit hi def link dylanRepeat Repeat hi def link dylanSimpleDefs Keyword hi def link dylanStatement Macro hi def link dylanString String hi def link dylanVariable Identifier let b:current_syntax = "dylan" " vim:ts=8