Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add minimal_init.lua #1006

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

kylo252
Copy link

@kylo252 kylo252 commented May 22, 2022

I saw that this is a common request, so I figured I can create a minimal template in Lua.

@hrsh7th
Copy link
Owner

hrsh7th commented Jun 14, 2022

@kylo252 Thank you for your cooperation!

I'm not familiar with packer.nvim, but I've seen packer.nvim cause caching issues.
Is there a cache problem with this minimum.lua?

The cache problem is that the plug-in is unintentionally loaded (even though you are not using this configuration file) or the plug-in remains out of date.

@David-Else
Copy link

I can recommend https://github.com/savq/paq-nvim , very minimal.

@kylo252
Copy link
Author

kylo252 commented Jun 18, 2022

I'm not familiar with packer.nvim, but I've seen packer.nvim cause caching issues. Is there a cache problem with this minimum.lua?

I'm not sure, but I don't think there are generally any such issues

cc: @wbthomason, @akinsho

@akinsho
Copy link

akinsho commented Jun 18, 2022

I'm not sure what the caching problems specifically relate to, but all I can provide is some general clarification on what people often perceive as caching.

  1. Usage of native vim packages - packer (and paq) use native vim packages which were added in vim 8 which means any plugins installed into the start directory which will be the case for anything not conditionally loaded will automatically be loaded by neovim on startup, packer does not control this behaviour

  2. The packer compiled file, this is only really relevant for conditionally loading plugins using autocommands or nvim commands and is not really relevant to start plugins. This file is read on startup and registers autocommands etc. to conditionally load plugins

I believe the caching issues are largely due to confusion around the behaviour of vim packages which differs from something like vim-plug which leads users to believe that packer is doing something rather than reverse which is that vim-plug works differently to native behaviour 🤷🏿

From what I can see there is no conditional loading here, so I don't know any reason why there would be any caching related issues

@Shougo
Copy link

Shougo commented Jun 19, 2022

I think the minimal init.lua or init.vim should not be depend on any of plugin mangers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants