Non-english completions

Question

Non-english completions

naquad opened this issue 10 years ago · 19 comments

Completion works fine with English characters, but it doesn't trigger with Russian while manual invocation of completion (<c-x><c-n>) works fine.

Answer 1 · 2014-12-07T21:35:09.000Z

It is feature. You want to complete non English characters, you must change g:neocomplcache#keyword_patterns variable.

Shougo/neocomplete.vim#316

Answer 2 · 2014-12-07T21:53:57.000Z

As I understand variable is g:neocomplcache_keyword_patterns['_'].
I've set it to [\kА-Яа-я]\+ (which works: :echo match('тест', '[\kА-Яа-я]\+')) that didn't help :(
Any clues?

UPD: file was text (test.txt)

Answer 3 · 2014-12-07T22:14:11.000Z

If you want to edit text filetype, you must change g:neocomplcache_keyword_patterns['text'].

Answer 4 · 2014-12-07T23:05:47.000Z

that didn't help either :(

Answer 5 · 2014-12-07T23:06:10.000Z

let g:neocomplcache_keyword_patterns['text']= '[\kа-яА-Я]\+' - not working

Answer 6 · 2014-12-07T23:44:59.000Z

I think you must regenerate cache by :NeoComplCacheClean.

Answer 7 · 2014-12-07T23:46:49.000Z

Didn't help.

Answer 8 · 2014-12-08T00:00:15.000Z

It is same behavior on neocomplete?
I don't want to change neocomplcache. But if neocomplete, I will check it.

Answer 9 · 2014-12-08T00:01:55.000Z

I don't have neocomplete and can't check it.

Answer 10 · 2014-12-08T00:04:42.000Z

Oh, I get it.
I think it is feature. Because, neocomplete or neocomplcache ignore multibyte input.

Answer 11 · 2014-12-08T00:05:18.000Z

It is neocomplete function. But neocomplcache is same.

function! neocomplete#is_multibyte_input(cur_text) "{{{
  return (exists('b:skk_on') && b:skk_on)
        \     || char2nr(split(a:cur_text, '\zs')[-1]) > 0x80
endfunction"}}}

Answer 12 · 2014-12-08T00:06:57.000Z

You cannot complete full multibyte input candidates like тест.

Answer 13 · 2014-12-08T00:07:03.000Z

Erm so basically it can't be fixed because you call that bug a feature? 0o

Answer 14 · 2014-12-08T00:08:19.000Z

It is not bug. It is intended feature. Because, current GVim IM integration is buggy.
Auto completion should not work on IM input. So, neocomplete/neocomplcache ignores multibyte input.

Answer 15 · 2014-12-08T00:11:01.000Z

Could you please add some option to turn this off? like g:neocomplcache_force_multibite or something

Answer 16 · 2014-12-08T00:11:52.000Z

I don't want to change neocomplcache code. Pull request is wellcome.

Answer 17 · 2014-12-08T00:17:11.000Z

I think the name should beg:neocomplcache_enable_multibyte_completion.

Answer 18 · 2014-12-08T00:20:55.000Z

https://github.com/naquad/neocomplcache.vim/commit/77d518050489e04a4197faf75f74405b8123b200

I've called it g:neocomplcache_allow_multibyte, but that can be changed. In any case that causes some unclear issue I can't figure out: completion looses last byte, i.e. was тест and suggestion is тес. Trying to figure it out.

Answer 19 · 2014-12-08T10:15:59.000Z

Well, neocomplcache has multibyte input bugs. Can you check it?