Eric Van Dewoestine wrote:
Any thoughts on this?
Bram?
For the most part I've gotten use to the behavior, but I still
occassionaly find my self hitting enter when I see the first entry
highlighted, and receive an ambiguous use error because the
highlighted entry isn't actually in the command line, only the longest
completion portion.
On 6/27/06, ervandew <[EMAIL PROTECTED]> wrote:
--- In [EMAIL PROTECTED], "Eric Van Dewoestine" <[EMAIL PROTECTED]>
wrote:
When starting vim as follows
vim -u NONE -c "set nocompatible | set wildmenu | set
wildmode=longest:full,full"
if you perform
:e<Tab>
you get a list of commands starting with 'e' and the command line is
unchanged (still only contains 'e').
The only issue, is that the first entry in the list is highlighted,
but the command line does not contain that text. The fact that the
entry is highlighted should indicate that the text is on the command
line and a <cr> will execute that command (like how ins-completion
works).
--
eric
--- End forwarded message ---
The default setting, wildmode=full , highlights (if anything) what it
actually completes. If you repeatedly hit the right-arrow key, it will
cycle through all full matches and what you had typed. See ":help
'wildmode'" for the various other possibilities. Whatever you see
highlighted on the statusline, what is filled-in is what you see on the
command-line. If "longest" is included, it's not necessarily a full
match. The purpose of that is to allow incremental completion.
Best regards,
Tony.
