On 02/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Gary Johnson <[EMAIL PROTECTED]> 写于 2006-11-02 15:55:34:
>
> This behavior might be affected by 'wildmode'. Mine is set to
> "longest,list". I also tried "longest,list:longest", but the
> behavior was the same.
>
> Regards,
> Gary
To make things clear, I had just tried:
vim -u NONE -U NONE
then :set nocp
(Must set nocompatible or the tab completion will be disabled.)
and then :help pre followed by <tab>
It works well, so the <tab> completion should be okay on default.
I've tried the above, but ":help pres<tab>" produces ":preserve". If
I then type 'i<tab>', it fails to find anything. I am hoping to get
":help pres<tab>i<tab>" to produce ":help 'preserveindent'".
As mentioned by Yakov, the problem seems to be down to it finding
matches that don't start at the start of the string. A little
frustrating when the only matches are 'preserveindent' and
'nopreserveindent'. To be honest, I'd be perfectly happy with the tab
completion being limited to matches at the start of the line (as long
as it ignored quotes, colons etc). However, the ideal (from my point
of view) would be to have it complete the longest common part,
regardless of where in the word it is.
Al
