Gombault Damien wrote:
I noticed a display bug with the completion menu.
If accented characters appears in the completion menu, some others characters
from the edited file appears too in the menu ! It's quite difficult to
explain so I've made some screenshots. You can also notice
' file.
Verify that 'fileencoding' is set to 'latin1'.
Insert a new line between #include and the begin of the /* comment. (o key)
Then type CTRL+x CTRL+i and the include completion menu appears like this :
http://img131.imageshack.us/img131/4117/vim5ls3.png
Another test :
'encoding' = latin1 and utf-8
. :)
Put the 3 files in the same directory.
Run Gvim, set your 'encoding' to 'latin1'.
Edit 3.cpp file.
Type, before the comment, CTRL-x CTRL-i for 'include' completion. Words
from 1.cpp are not displayed in the completion menu because words are not
converted to the current encoding.
Run Gvim, set
and set your 'encoding' to 'utf-8'.
Edit the '2.cpp' file.
Verify that 'fileencoding' is set to 'latin1'.
Insert a new line between #include and the begin of the /* comment. (o key)
Then type CTRL+x CTRL+i and the include completion menu appears like this :
http://img131.imageshack.us/img131/4117
On 1/23/07, Marc Weber [EMAIL PROTECTED] wrote:
It would be convinient to get an item from the completion menu faster
than downdown .. or typing more characters.
What do you think of prepending each item with a number and add a
key-mapping
c-iidx to get the idxth item?
so c-i4 would select
It would be convinient to get an item from the completion menu faster
than downdown .. or typing more characters.
What do you think of prepending each item with a number and add a
key-mapping
c-iidx to get the idxth item?
so c-i4 would select the 4th.
Would it be convinient to add another
All,
Recently I was appreciating the beauty of using pumvisible() to setup
all kinds of mappings for the completion menu (ex. enter to do c-y).
I noticed when messing around with all of that, that space actually
exits the menu. Is this the desired behavior? Sometimes I am doing line
completion
Hi!
As you've probably all noticed the completion menu flickers when you
move through the items rapidly. Why is this? Is it really necessary
to redraw the whole completion menu when it really only should require
redrawing the item previously selected and the item selected now [1]?
Anyway
-menu, because it takes at least .2 seconds to redraw each time I press
CTRL-N.
regards,
Peter
--- Nikolai Weibull [EMAIL PROTECTED] wrote:
Hi!
As you've probably all noticed the completion menu flickers when you
move through the items rapidly. Why is this? Is it really
Robert Webb wrote:
When I use Ctrl+P to complete a word in insert mode, then hit space or
Esc because I'm happy with the match, not waiting for the menu to pop
up with every possible match (ie while it's still searching through
header files etc), the menu then still flashes up briefly, even
Robert Webb wrote:
When I use Ctrl+P to complete a word in insert mode, then hit space or
Esc because I'm happy with the match, not waiting for the menu to pop
up with every possible match (ie while it's still searching through
header files etc), the menu then still flashes up briefly, even
When I use Ctrl+P to complete a word in insert mode, then hit space or
Esc because I'm happy with the match, not waiting for the menu to pop
up with every possible match (ie while it's still searching through
header files etc), the menu then still flashes up briefly, even though
the
the user are
selecting menu items with C-N/C-P, and at this time, Enter is
normally assumed as a confirm of the selection. And I think it is very
common a user interface convention.
I think it is worth breaking the compatibility between vim6.x and
vim7 since there is no completion menu in vim6.x
Georg Dahn wrote:
Ok, let's assume there are several completions, such that you get a menu
with C-N. Then if you move the selection with the cursor keys and
press Enter, the selected item is being chosen. If you do the same
with C-N (instead of using cursor keys), Enter inserts a new
14 matches
Mail list logo
