Understand the VerzLazy event

[tummetott]

Hello,
i'd like to understand the VeryLazy event.

The README states:

VeryLazy: triggered after LazyDone and processing VimEnter auto commands

So far so good. But what do we achieve with this? Isn't everything loaded at this event effectivly also loaded during the startup of vim? Where is the difference between VeryLazy and no lazy loading? Isn't the effective load work that vim has to do on startup the same when we just don't lazyload?

Or is the readon asynchronicity? Everything loaded on VeryLazy is done async?

Thank you

[folke]

It is indeed!

The distinction is that you probably want some plugins to load that are needed to render the Neovim ui, so you want all those plugins to be loaded during startup as quickly as possible.

Some other plugins that don't affect the ui, can load after that.

Obviously, you can just not use VeryLazy and just load everything on VimEnter or with lazy=false instead. It all depends on how important time to first draw is important to you.

[tummetott]

Thank you @folke for the fast reply.

It all depends on how important time to first draw is important to you.

If course I want everything to be as snappy as possible, thats why I ask 😃

It is indeed!

This refers to the async question?

So to wrap things up: I'm already lazyloading 2/3 of my plugins where I know that I don't need them at startup. Now I'm left with ~20 plugins that i thought I need at startup. I'm now trying to figure out which one to load at VeryLazy.
Plugins for the statusline, colorscheme, scrollbar, greeter, treesitter (for highlighting), gitsigns are better not to be lazy loaded at all because they affect the ui. Is that right? And then i load everything else on VeryLazy?

This is the list of plugins that are not lazyloaded, because they load at start or they are a dependency of a plugin that loads at start. Maybe you can give me a hint how to proceed with them. The heavy ones are

• lspconfig
• treesitter
• base16 (colorscheme)
• feline (statusline)

    ● alpha-nvim 1.09ms   start
    ● cmp-nvim-lsp 0.14ms   nvim-lspconfig
    ● dressing.nvim 2.06ms   start
    ● feline.nvim 12.53ms   start
    ● fidget.nvim 5.32ms   start
    ● gitsigns.nvim 9.01ms   feline.nvim
    ● indent-blankline.nvim 5.48ms   start
    ● lazy.nvim 28.21ms   init.lua
    ● mason-lspconfig.nvim 0.63ms   nvim-lspconfig
    ● mason.nvim 0.86ms   nvim-lspconfig
    ● neodev.nvim 0.61ms   nvim-lspconfig
    ● nvim-base16 16.41ms   start
    ● nvim-lspconfig 20.5ms   start
    ● nvim-scrollbar 4.08ms   start
    ● nvim-surround 3.52ms   start
    ● nvim-treesitter 18.09ms   start
    ● nvim-treesitter-endwise 1.32ms   nvim-treesitter
    ● nvim-treesitter-textobjects 8ms   nvim-treesitter
    ● nvim-treesitter-textsubjects 1.58ms   nvim-treesitter
    ● nvim-web-devicons 0.73ms   feline.nvim
    ● restore_view.vim 0.45ms   start
    ● vim-qf 1.68ms   start
    ● which-key.nvim 2.34ms   start

Thank you

[folke]

Just look at LazyVim's plugins for ideas https://github.com/LazyVim/LazyVim/tree/main/lua/lazyvim/plugins