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

Completion menu is covered by other lower priority popup #1049

Closed
obcat opened this issue Jan 15, 2021 · 2 comments
Closed

Completion menu is covered by other lower priority popup #1049

obcat opened this issue Jan 15, 2021 · 2 comments

Comments

@obcat
Copy link
Contributor

obcat commented Jan 15, 2021

Describe the bug

The zindex of insert mode completion menu is 100, but it is covered by other popup with lower zindex value, such as 10.

To Reproduce

  1. Run vim -N -u minimal_vimrc.

    " minimal_vimrc
    call plug#begin()
    Plug 'prabirshrestha/asyncomplete.vim'
    Plug 'prabirshrestha/vim-lsp'
    call plug#end()
  2. Create a popup with zindex of 10.

    :call popup_create(['xxx', 'xxx'], {'zindex': 10})
  3. Show completion menu around the popup.

  4. Completion menu is covered by the popup.

Screenshots

ss 2021-01-16 3 44 14

(Highlighted popup for clarity)

Expected behavior

Completion menu is not covered by lower priority popup.

Environment

  • Vim 8.2.2300
  • macOS Catalina (version 10.15.7)
  • iTerm2

Additional context

The fact that the zindex of completion menu is 100 is mentioned before :h popup-props.

Depending on the "zindex" the popup goes under or above other popups.  The
completion menu (|popup-menu|) has zindex 100.
@prabirshrestha
Copy link
Owner

completion menu is using default vim completion menu. so nothing we can do here. if you are manually creating a popup you can get the position and width/height of the complete menu and position it correctly.

not a bug in vim-lsp

@obcat
Copy link
Contributor Author

obcat commented Jan 23, 2021

I supposed this was a bug in either vim-lsp or asyncomplete.vim, since I couldn't reproduce it without them.
I wonder if this is caused by unknown bug in Vim.

Anyway, I understood that this cannot be fixed. Thank you.

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