Replies: 2 comments 4 replies
-
I write the plugin config in a separate file and load it. -- onedark.lua
return {
'navarasu/onedark.nvim',
commit = 'df090f9d72d43aa51dec5760c44da288b58a79b6',
config = function()
require("onedark_config")
end,
} -- onedark_config.lua
local onedark = require('onedark')
onedark.setup({
style = 'darker',
})
onedark.load() |
Beta Was this translation helpful? Give feedback.
0 replies
-
EDIT: removing this... it had other issues |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been trying to organize my setup to use config functions for setup. Aside from preventing sync issues when plugins aren't installed, it just feels like a saner strategy for managing everything than including everything in the packer config and then spreading out the config logic in other files. It should preclude any issues with things being out of sync, etc.
I've found that the contents of
packer_compiled.lua
contain a compiled version of these functions:However, this content is not updated by
:PackerSync
when something changesSo far, deleting
packer_compiled.lua
and then rerunning:PackerCompile
is the only way I have found to refresh it. Does anyone have a more idiomatic solution for this? I can throw a command together to do that, but I feel like surely I'm not the first to encounter this...Beta Was this translation helpful? Give feedback.
All reactions