Is There Supposed to be Autocomplete for Neovim Plugins? #1714
Unanswered
ScumbagScalawag
asked this question in
Q&A
Replies: 1 comment
-
If you want you can leverage But for plugins, unless the plugin provider will bother to create a second plugin with auto completions / lsp support for their plugin, then I don't think it'll going to happen. Usually plugins themselves use lua type annotations, so you could go into their source code and copy-paste the type annotation but i think that would be more trouble than its worth |
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.
-
TLDR; Is there a way to have the auto-complete and/or linting for the tables/properties listed in
:h lazy.nvim-🔌-plugin-spec
? Or even plugin-specificopts
tables?I find it very frustrating that I have to look at
:h lazy.nvim-🔌-plugin-spec
every time I need to add something simple to lazy.nvim.Same for every plugins' docs to even know what properties/tables exist inside of
opts
.For example, there is no helpful auto-complete available (with my setup) for "where can I go from here".

Same goes for the

opts
table:Any advice is helpful 🙏🏼
Beta Was this translation helpful? Give feedback.
All reactions