Replies: 1 comment
-
I have no idea what you're asking. you can organize your neovim config anyway you like. just try and use what works best for you. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is it possible to put config together as a "plugin" in the structure of real plugins for the sake of consistency? For example, I have a diagnostics.lua file that configures builtin Neovim diagnostic and would like to put in plugins/ folder that gets loaded automatically. All the configuration in that file does not relate to any real plugins, so it doesn't seem appropriate to put it in e.g. lsp.lua where it might have lsp-related plugins (diagnostic is not necessarily lsp) where I would do such configuration at the top of the file and then return the table of plugin specs for Lazy.
E.g. I was thinking of maybe Lazy can just require the file automatically in plugins/ if it does not return a plugin spec. Or maybe this is entirely inappropriate and I should just
require "my.diagnostic"
in ~/.config/nvim/lua/my/init.lua.Beta Was this translation helpful? Give feedback.
All reactions