doesn't work with YCM for python3?

[NewUserHa]

I typed prin <tab> <enter> ( ' 123 ' )

there's nothing dispalying during the tyeping in statebar which I already set cmdheight=2
my c-y is 'already at newest change'

thanks!

[Shougo]

Please upload your v:completed_item value after completed.

Please upload your minimal init.vim.

If not, I will close your issue.

[NewUserHa]

v:completed_item {}
what's minimal init.vim?

[Shougo]

v:completed_item {}

?

Hm. You should use autocmd to capture it.

autocmd CompleteDone * echomsg string(v:completed_item)

what's minimal init.vim?

Well, have you enabled echodoc?

[NewUserHa]

logging.debu..
{'word': 'deb', 'menu':'', 'user_data':'', 'info':'', 'kind':'', 'abbr':''}
oh, I see the debug(msg, *arg, **kwargs) only when there's a parenthese after the logging.debug, and it disappear instantly if I type anything inside the paraness even a single quote.
can you keep that until next complete start?

I typed the ( and ' shortly just now.

and the c-y in readme.md doesn't work. or just can't work with YCM?

[Shougo]

Hm. If so, I cannot support YCM.
Sorry.

[NewUserHa]

can you keep the output of echodoc.vim until next complete start? it's inconvenient.

[Shougo]

Why it is needed?
It adds the flicker.

[Shougo]

I have added g:echodoc#enable_force_overwrite option.

[Shougo]

and the c-y in readme.md doesn't work. or just can't work with YCM?

I don't test YCM. So I don't recommend to use it with echodoc.
deoplete is recommended and tested well.

[NewUserHa]

echodoc still works good with jedi-vim.
but echodoc dispaly nothing with YCM since the path 'f1f711b', and g:echodoc#enable_force_overwrite seems not working.

[Shougo]

Sorry, I cannot support YCM.

[Shougo]

I think YCM overwrites the command line.