> Thanks for the clear example. I'm now able to reproduce the problem.
>
> There are actually two problems. One is that text with non-printable
> characters causes trouble in the popup menu. I'll fix that now (see
> patch below).
>
> The other is that completions obtained from a file in another
Gombault Damien wrote:
> > A few questions:
> >
> > - What is 'encoding' set to?
> > - What is the actual text in the entries with problems? Give this
> > byte-for-byte. You may need to insert an entry to find out.
> > - Can you reproduce it by setting 'omnifunc' to a simple function that
> >
Another test with 3 files :
"1.cpp" : UTF-8 file with French accented characters.
"2.cpp" : the same file but with Latin-1 charset.
"3.cpp" : a file to test 'include' completion.
Yes, it's a bit strange because it's not a great idea to work with different
encodings. But it shows the prob
> A few questions:
>
> - What is 'encoding' set to?
> - What is the actual text in the entries with problems? Give this
> byte-for-byte. You may need to insert an entry to find out.
> - Can you reproduce it by setting 'omnifunc' to a simple function that
> returns a fixed list of text entries
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 the
Hello.
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 these "bad"
characters appear
