Conditional plugin activation for VSCode Neovim support #1656
Unanswered
raj-magesh
asked this question in
Q&A
Replies: 2 comments
|
I meant to reply to this much earlier, must've forgotten. Could you please try this option? |
0 replies
|
lazy.plugins.*.enabled is usually more apt than what @NotAShelf recommended For plugins provided by nvf, the configuration may or may not make use of lazy.plugins. You'll have to check the source to see if that's the case. If said plugin is configured via lazy.plugins, lazy.plugins.*.enabled will work for you. Otherwise, you'll have to configure the plugin yourself, with the |
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.
I have
nvfinstalled and everything is great, but I'd also like to use the VSCode Neovim plugin for VSCodium. However, some plugins shouldn't be activated when in VSCode.The recommended approach with a Lua configuration is the following.
Is there an equivalent with nvf?
All reactions