You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 13, 2021. It is now read-only.
When the space at either side of the completion list is too narrow, the documentation floating-window gets behind completion list, having part of the text impossible to read.
My testing minimal init.vim
" nvim-lspconfigluarequire('lspconfig').pyls.setup{}
" completion-nvimautocmdFileTypepythonluarequire('completion').on_attach()
letg:completion_matching_strategy_list= ['exact', 'substring', 'fuzzy']
letg:completion_matching_ignore_case=1" not v:true, 1. ¯\_(ツ)_/¯letg:completion_matching_smart_case=1" not v:true, 1. ¯\_(ツ)_/¯letg:completion_trigger_on_delete=1" not v:true, 1. ¯\_(ツ)_/¯
How to reproduce
Have launched vim in a 80 column terminal
Intent a line as if you needed to write your first character around column 40 (half of the width of the terminal)
Start typing and select some of the completions
Sometimes the documentation window gets underneath the completion list like this:
Expected behavior
Not having documentation underneath the list of completions because it makes it impossible to read.
The text was updated successfully, but these errors were encountered:
baco
changed the title
Whith narrow screen, completion list of methods overlaps the documentation window
With narrow screen, completion list of methods overlaps the documentation window
Mar 24, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When the space at either side of the completion list is too narrow, the documentation floating-window gets behind completion list, having part of the text impossible to read.
My testing minimal init.vim
How to reproduce
Expected behavior
Not having documentation underneath the list of completions because it makes it impossible to read.
The text was updated successfully, but these errors were encountered: