Changed my mind to try 'lazy.nvim'. It seems to better support dependency handling and Lua plugins. Thank you for the replies!
OTOH, while I've been using Neovim with NvChad recently (since I didn't have time to do this before), I think I'll start from scratch and port the config I have for plain old Vim. I'll stick to 'vim-plug' on #vim.
My intention is to use #neovim as a proper dev environment with decent LSP and DAP support. As an early supporter, it makes me happy how far neovim has come.
Move over VS Code. 😋 I have updated my #neovim editor configuration from scratch. Now with functional parity of my vim setup, but with newer Lua plugins, LSP & DAP client support, better syntax handling & code/text completion, and more.
Changed my mind to try 'lazy.nvim'. It seems to better support dependency handling and Lua plugins. Thank you for the replies!
OTOH, while I've been using Neovim with NvChad recently (since I didn't have time to do this before), I think I'll start from scratch and port the config I have for plain old Vim. I'll stick to 'vim-plug' on #vim.
My intention is to use #neovim as a proper dev environment with decent LSP and DAP support. As an early supporter, it makes me happy how far neovim has come.
Move over VS Code. 😋 I have updated my #neovim editor configuration from scratch. Now with functional parity of my vim setup, but with newer Lua plugins, LSP & DAP client support, better syntax handling & code/text completion, and more.
Finally decided to use a separate config setup for #neovim (from vim). Want to avoid relying on VS Code for good LSP support.
Planning on using 'vim-plug' since I've used it for a long time. Are there any particular functional reasons why I should consider 'lazy.nvim' instead?
Changed my mind to try 'lazy.nvim'. It seems to better support dependency handling and Lua plugins. Thank you for the replies!
OTOH, while I've been using Neovim with NvChad recently (since I didn't have time to do this before), I think I'll start from scratch and port the config I have for plain old Vim. I'll stick to 'vim-plug' on #vim.
My intention is to use #neovim as a proper dev environment with decent LSP and DAP support. As an early supporter, it makes me happy how far neovim has come.
Finally decided to use a separate config setup for #neovim (from vim). Want to avoid relying on VS Code for good LSP support.
Planning on using 'vim-plug' since I've used it for a long time. Are there any particular functional reasons why I should consider 'lazy.nvim' instead?