From 5cca44e8f58b1ec8967efeae0a61d9fd2f2bdaaf Mon Sep 17 00:00:00 2001 From: PowerUser64 Date: Fri, 7 Jan 2022 12:21:24 -0800 Subject: [PATCH] nvim: new plugin loading idea --- .config/nvim/init.lua | 27 +++++++++++++++++++++------ 1 file changed, 21 insertions(+), 6 deletions(-) diff --git a/.config/nvim/init.lua b/.config/nvim/init.lua index dfb8da7..0950909 100644 --- a/.config/nvim/init.lua +++ b/.config/nvim/init.lua @@ -7,13 +7,28 @@ require('blake.settings') -- TODO: -- Make plugins more modular --- - Have a file with toggles for all plugins --- - If a plugin toggle is off, --- - the configuration for it should not be run, --- - and the plugin should not be loaded +-- - Have a file with toggles for all plugins +-- - If a plugin toggle is off, +-- - the configuration for it should not be run, +-- - and the plugin should not be loaded +-- Downsides: +-- - requires me to add the plugin in two places (one in the plugin list, and again in the toggle list) -- OR --- - Find out how to get a list of loaded plugins --- - Load the configuration for each plugin +-- - Find out how to get a list of loaded plugins +-- - Load the configuration for each plugin +-- Downsides: +-- - May not be plugin manager-independent +-- OR +-- - Create a file for each plugin that requires configuration and load them from their own files. +-- - I think this would be the most modular approach, as it would make my config more independent specific plugin managers. +-- Downsides: +-- - Lots of files (could be a good thing) +-- OR +-- - Make a list of plugins ('tpope/surround' style) +-- - load all plugins using whatever plugin manager in a for loop +-- - in the for loop, optionally load the configuration for each plugin based on its name +-- Downsides: +-- - Hardest (requires me to make a for loop, and I don't know lua) -- Plugins to install: -- lightspeed.nvim -- lightbulb?