Mercurial > vim
view runtime/ftplugin/vroom.vim @ 11285:0b4adcfb7b25 v8.0.0528
patch 8.0.0528: highlight wrong text when 'wim' includes "longest"
commit https://github.com/vim/vim/commit/ef8eb0897819099fb00d675afb9bffe1d008c45e
Author: Bram Moolenaar <Bram@vim.org>
Date: Thu Mar 30 22:04:55 2017 +0200
patch 8.0.0528: highlight wrong text when 'wim' includes "longest"
Problem: When 'wildmenu' is set and 'wildmode' has "longest" then the first
file name is highlighted, even though the text shows the longest
match.
Solution: Do not highlight the first match. (LemonBoy, closes #1602)
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Thu, 30 Mar 2017 22:15:04 +0200 |
parents | 1e8ebf870720 |
children |
line wrap: on
line source
" Vim filetype plugin file " Language: Vroom (vim testing and executable documentation) " Maintainer: David Barnett (https://github.com/google/vim-ft-vroom) " Last Change: 2014 Jul 23 if exists('b:did_ftplugin') finish endif let b:did_ftplugin = 1 let s:cpo_save = &cpo set cpo-=C let b:undo_ftplugin = 'setlocal formatoptions< shiftwidth< softtabstop<' . \ ' expandtab< iskeyword< comments< commentstring<' setlocal formatoptions-=t " The vroom interpreter doesn't accept anything but 2-space indent. setlocal shiftwidth=2 setlocal softtabstop=2 setlocal expandtab " To allow tag lookup and autocomplete for whole autoload functions, '#' must be " a keyword character. This also conforms to the behavior of ftplugin/vim.vim. setlocal iskeyword+=# " Vroom files have no comments (text is inert documentation unless indented). setlocal comments= setlocal commentstring= let &cpo = s:cpo_save unlet s:cpo_save