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

Visual glitch when window is resized with which key open #137

Open
gbrlsnchs opened this issue Jul 30, 2020 · 0 comments
Open

Visual glitch when window is resized with which key open #137

gbrlsnchs opened this issue Jul 30, 2020 · 0 comments

Comments

@gbrlsnchs
Copy link

gbrlsnchs commented Jul 30, 2020

Environment (please complete the following information):

  • OS: Void Linux (kernel 5.7)

  • Neovim version: 0.5.0 (nightly)

  • Have you reproduced with a minimal vimrc: yes

Describe the bug
When the vim-which-key floating window is open and you resize the editor window, the editor window goes blank unless a button is pressed. Also, the floating window is not resized accordingly, so sometimes when the screen is back after pressing a button, the floating window is sized wrongly.

To Reproduce
Steps to reproduce the behavior:

  1. Create the minimal vimrc min.vim:
set nocompatible
set runtimepath^=/path/to/vim-which-key
syntax on
filetype plugin indent on

let mapleader = "\<Space>"
let g:which_key_map =  {
      \ 'b': {
      \   'name': '+buffer',
      \   'n': ['bnext', 'next-buffer'],
      \  }
      \ }
call which_key#register('<Space>', "g:which_key_map")
nnoremap <silent> <Leader> :WhichKey '<Space>'<CR>
  1. Start (neo)vim with command: vim -u min.vim

  2. Type Space and resize the editor (Vim) window

  3. The buffer is visually clear (nothing is shown) until a button is pressed

Expected behavior
On resize, either the floating window closes and preservers the editor window intact or it resizes accordingly without glitching the editor window.

Additional context
I am using a WM called bspwm, and am simply toggling between monocle view and two panes split vertically.

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

1 participant