Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing highlight update in popup completion menu #217

Open
dan-t opened this issue May 26, 2021 · 4 comments
Open

Missing highlight update in popup completion menu #217

dan-t opened this issue May 26, 2021 · 4 comments

Comments

@dan-t
Copy link

dan-t commented May 26, 2021

When I'm pressing TAB in the popup completion menu, then the next entry is chosen and displayed at the cursor, but the highlighting in the popup menu isn't updated and still at the previous entry. If I'm instead pressing C-N then both gets correctly updated.

I'm getting the same behavior with vim 8.1 and gvim 8.1 on Ubuntu 20.04 with the current github version of supertab (commit f0093ae).

Any ideas?
Thanks for any help!

By the way, I'm loving supertab and might use it already for longer than a decade! :)

@ervandew
Copy link
Owner

if you run :version in vim, what does the Included patches: line show?

@ervandew
Copy link
Owner

woops, missed that you are on 8.1, not 8.2. hmm, not sure what would cause that. do you have any other plugins that you can disable to see if the problem goes away?

@dan-t
Copy link
Author

dan-t commented Jun 1, 2021

I've found the issue, the reason is a hack I've applied.

I want to have 'set completeopt=' for the case
and 'set completeopt=menuone,longest' for the case.

So I've hacked this setting into the beginning of the SuperTab
function and at the beginning of the omni-completion function,
and this causes the described issue.

Would it somehow be possible to have different 'completeopt'?

@dan-t
Copy link
Author

dan-t commented Jun 1, 2021

I've found the issue, the reason is a hack I've applied.

I want to have 'set completeopt=' for the case <c-p>
and 'set completeopt=menuone,longest' for the case <c-x><c-o>.

So I've hacked this setting into the beginning of the SuperTab
function and at the beginning of the omni-completion function,
and this causes the described issue.

Would it somehow be possible to have different 'completeopt'?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants