Neovim

• nvim --version:

NVIM v0.5.0-dev+1339-g5d9c56012
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/T
ools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe /DWIN32 /D_WINDOWS /W3 /MD /Zi /O2
/Ob1 /DNDEBUG /W3 -D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC

Neovide should remember the last window dimension and open the new window with the same dimensions.
Could be a setting like g:neovide_remember_dimensions

Move 95% of readme to a comprehensive wiki.

Only keep pictures, description of features, example of lv-config.lua, install script and link to the wiki

I think everything from telescope.path can already be found in plenary.path so we should use that module instead and remove telescope.path

For the longest time I was able to access the pry console while running tests using :TestNearest, but it hasn't been working of late. I am able to run tests using :TestNearest and the other vim-test commands. My issue is that if I throw in a binding.pry in the test, I don't see the pry console open up anymore in the test window. That used to work before, and I can't figure out why. I'm

While I quite like the information readily provided by g:lsp_diagnostics_float_cursor and g:lsp_diagnostics_echo_cursor, their automatic nature doesn't fit my workflow.

Would it be difficult to add an avenue to trigger them on-demand, similar to <plug>(lsp-hover) / :LspHover?

Along similar lines, would it be difficult to add a g:lsp... setting to have <plug>(lsp-next-diganostic)