IMHO no particular choice can satisfy everyone. Happily we have the
vimrc to change the defaults which are not to our personal taste. For
instance the vimrc_example.vim (or the defaults.vim nowadays) has
":filetype plugin indent on" but just after calling it my vimrc has
":filetype indent off". Similarly my vimrc has
if has('wildmenu')
set wildmenu
if exists('+wildmode')
set wildmode=longest:full,full
endif
if !has('gui_running')
runtime! menu.vim
set wildcharm=<C-Z>
map <F10> :emenu <C-Z>
imap <F10> <C-O>:emenu <C-Z>
endif " ! !has('gui_running')
endif " 'wildmenu'
So what's the problem?
Best regards,
Tony.
On Wed, May 9, 2018 at 10:24 AM, Christian Brabandt <[email protected]> wrote:
> Bram,
> can we please change the default for wildmode from "full" to
> "list:longest,longest:full"?
>
> Rationale: I have been working lately on a system with many files laying
> around with complex names across a complex directory structure. On that
> system I did not have my current vimrc config files around, only using
> the vim that comes with git-bash.
>
> However since I need to edit specific files it drives me actually nuts,
> that the filename completion will complete to some random files and
> there is no easy way to go back to the uncompleted typed filename so I
> have to smash backslash until I find from where to correct the pattern
> (plus one actually has to stare at the completed filename pattern and
> double check that the completed name is actually the correct one).
>
> I think only to complete the longest common match is a much more
> sensible behaviour and does not cause confusion. In fact, sometimes I
> did not even notice that Vim was completing the wrong filename for me,
> until I wondered why I didn't find what I was looking for.
>
> Attached patch does this change to defaults.vim
>
> Best,
> Christian
> --
> Testfahrer der A-Klasse schuften bis sie umkippen.
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
