4 ms·

After years of using Vim as a keyboard assassin, then Neovim (with a custom config initially based on kickstart.nvim), about a month ago I started using LazyVim

by wyclif 2y ago

After years of using Vim as a keyboard assassin, then Neovim (with a custom config initially based on kickstart.nvim), about a month ago I started using LazyVim. After test-driving the default config for just a few hours, I found myself nodding my head and saying to myself, "Yes, this is the way." I had seen some of the other "Neovim as IDE" projects but after looking at them carefully, I decided that LazyVim is generally the most polished one out there. Folke deserves a lot of credit. The breakthrough for me was realising that it's a totally acceptable tradeoff to let other developers who know what they're doing, keep up with the bleeding edge plugin scene, and have generally good opinions make decisions about configuration so I can get real work done and not spend time getting bogged down in ricing and config files.

djasnowski 2y ago
Agreed. I use to switch on and off between vim, neovim and VS Code vim-keybindings until I found AstroVim. When I use AstroVim, I can modify what little I need to knowing the base and foundation is taken care of and I can focus on what matters.
Filligree 2y ago
I tries LazyVim, but on every startup it nags me about version updates, and :x somehow takes 2-3 seconds extra as well. I don't live in the editor; vim is only useful to me if it starts up and quits instantly.
- wyclif 2y ago
  It sounds like you don't have lazy loading enabled. No way it should take that long to start up, and version updates shouldn't be that frequent.
  - Filligree 2y ago
    I don't know how to enable it. It isn't mentioned on the config screen, though not very much is.
    - wyclif 2y ago
      How much ricing have you done of the default config? Lazy loading of plugins is enabled by default— you shouldn't have to do anything. LazyVim handles lazy loading automatically; you don't need to manually configure anything. It should look like this: -- lazy.nvim configuration example require('lazy').setup({ defaults = { lazy = true, -- default to lazy loading -- other default options }, plugins = { { 'neovim/nvim-lspconfig' }, { 'hrsh7th/nvim-cmp' }, -- ... other plugins } })
- Tmpod 2y ago
  You can disable the update checker with a very simple config change.[0] As for :x being slow, I'm not sure what that might be, it certainly isn't the case for me, it quits instantly. Try asking around in their support channels? [0]: https://www.lazyvim.org/configuration/lazy.nvim https://www.lazyvim.org/configuration/lazy.nvim (look for "checker" field)

by wyclif 2y ago

djasnowski 2y ago

Agreed. I use to switch on and off between vim, neovim and VS Code vim-keybindings until I found AstroVim. When I use AstroVim, I can modify what little I need to knowing the base and foundation is taken care of and I can focus on what matters.

Filligree 2y ago

I tries LazyVim, but on every startup it nags me about version updates, and :x somehow takes 2-3 seconds extra as well. I don't live in the editor; vim is only useful to me if it starts up and quits instantly.

wyclif 2y ago
It sounds like you don't have lazy loading enabled. No way it should take that long to start up, and version updates shouldn't be that frequent.
- Filligree 2y ago
  I don't know how to enable it. It isn't mentioned on the config screen, though not very much is.
  - wyclif 2y ago
    How much ricing have you done of the default config? Lazy loading of plugins is enabled by default— you shouldn't have to do anything. LazyVim handles lazy loading automatically; you don't need to manually configure anything. It should look like this: -- lazy.nvim configuration example require('lazy').setup({ defaults = { lazy = true, -- default to lazy loading -- other default options }, plugins = { { 'neovim/nvim-lspconfig' }, { 'hrsh7th/nvim-cmp' }, -- ... other plugins } })
Tmpod 2y ago
You can disable the update checker with a very simple config change.[0] As for :x being slow, I'm not sure what that might be, it certainly isn't the case for me, it quits instantly. Try asking around in their support channels? [0]: https://www.lazyvim.org/configuration/lazy.nvim https://www.lazyvim.org/configuration/lazy.nvim (look for "checker" field)