refactor(pack): BREAKING CHANGE, migrate to lazy.nvim as package manager.

[ayamir]

No description provided.

[ayamir]

A weird problem:

[ayamir]

A weird problem:

Also appears for main branch, so it's a upstream issue and have nothing to do with lazy.nvim.

[ayamir]

vim-startuptime -vimpath nvim -count 100 test result with lazy load all of plugins:

[Jint-lzxy]

🎉 Will test this PR after other changes are made. There might be some corner cases to consider.

[nullchilly]

A weird problem:

nvimdev/lspsaga.nvim#720

Edit: Already been done here 6f3eddb 😅

[ayamir]

colorscheme can be lazy loaded for lazy.nvim.

[Jint-lzxy]

colorscheme can be lazy loaded for lazy.nvim.

@ayamir I didn't set lazy load for catppuccin because it is listed as the colorscheme that would be tried to load when starting an neovim instance.

Doc from lazy.nvim:

-- try to load one of these colorschemes when starting an installation during startup
colorscheme = { "habamax" },

[Jint-lzxy]

The issue: #426 about plugins not being loaded when creating a new empty buffer/named file has been resolved. At the same time, the loading sequence has also been optimized to try to load as few plugins as possible before UIEnter. Except for GitHub action, which has not been written, this PR LGTM 👍

[Jint-lzxy]

After merging these commits, we should also remind users to remove packer-related files. rm -rf ~/.local/share/nvim/site/pack

[nullchilly]

Suggession: Remove config.lua and use https://github.com/folke/lazy.nvim#-structuring-your-plugins, looks much cleaner and easier to maintain IMO: https://github.com/LazyVim/LazyVim/tree/main/lua/lazyvim/plugins

[CharlesChiuGit]

Suggestion: Remove config.lua and use folke/lazy.nvim#-structuring-your-plugins, looks much cleaner and easier to maintain IMO: LazyVim/LazyVim@main/lua/lazyvim/plugins

I use this kind of structure in my personal config too, it's indeed much easier to maintain.
However, there's one small down side. Splitting config.lua into multiple files will cause the time for sumneko_lua to process all workspace's file to increase a bit, at least when using packer. Personally, I'm willing to trade a slightly increased diagnostic time for a better structure.

[CharlesChiuGit]

Ok, let me see if i can reproduce it on another machine. Or maybe it's just a one-time thing.

After pulling the latest commit on this branch, that error didn't happened again. Maybe it's just a one-time error or Jint-lzxy fixed it.

[Jint-lzxy]

Suggestion: Remove config.lua and use folke/lazy.nvim#-structuring-your-plugins, looks much cleaner and easier to maintain IMO: LazyVim/LazyVim@main/lua/lazyvim/plugins

I use this kind of structure in my personal config too, it's indeed much easier to maintain. However, there's one small down side. Splitting config.lua into multiple files will cause the time for sumneko_lua to process all workspace's file to increase a bit, at least when using packer. Personally, I'm willing to trade a slightly increased diagnostic time for a better structure.

Sounds great! IMO the issue related to lua-language-server is trivial - ensuring that the file structure is easier to maintain should be of first priority. Changes will be pushed in a few days 👍

btw, happy Chinese New Year 🥳 新年快乐，兔年大吉！

[CharlesChiuGit]

Happy lunar new year!

[ayamir]

新年快乐！

[nullchilly]

Happy lunar new year! (I'm from Vietnam :)

[Jint-lzxy]

@ayamir @CharlesChiuGit I've implemented the first draft of #425 (comment). The action log can be found here.

The following changes have been made:

• Install script now checks and supports non-interactive installation;
• CI file added (has write access).

CI has the following characteristics:

• Update the lock file at 01:30 UTC (09:30 CST) every day;
• Changes are commited by github-actions[bot];
• Check the files before updating (see the source code for more information)
• The lockfile is updated only when the CI is executed in the parent repository (i.e., ayamir/nvimdots) and current branch is main.

I will push these changes if there are no issues 👍

[CharlesChiuGit]

I don't have pc around me in a few days. Will check once i got home.

[ayamir]

@ayamir @CharlesChiuGit I've implemented the first draft of #425 (comment). The action log can be found here.

The following changes have been made:

• Install script now checks and supports non-interactive installation;
• CI file added (has write access).

CI has the following characteristics:

• Update the lock file at 01:30 UTC (09:30 CST) every day;
• Changes are commited by github-actions[bot];
• Check the files before updating (see the source code for more information)
• The lockfile is updated only when the CI is executed in the parent repository (i.e., ayamir/nvimdots) and current branch is main.

I will push these changes if there are no issues 👍

No problem, I want to merge this pr as soon as possible.

[Jint-lzxy]

This PR LGTM 🍊

Minor updates such as #425 (comment) will be pushed in the form of patches later 👍

[CharlesChiuGit]

So will the config.lua split into multiple files in the future?

[Jint-lzxy]

So will the config.lua split into multiple files in the future?

Yes, but IMO we should first discuss how to classify these configs.

[CharlesChiuGit]

ok, i'll open a draft and perhaps we can discuss there.