On Do, 07 Jan 2021, David Lowry-Duda wrote:
> Aside from startup time (especially if plugins don't use autoload), unused > plugins should barely affect speed. But I'll note that it's pretty > straightforward to profile vim to see what is taking time and clock cycles, > in case you want to actually examine one or more > suspicious plugins and determine what is causing slowness. However depending on where your plugins reside, it may take a considerable amount of time to read in all your files. For that reason, I am especially mad at vim-airline and vim-airline-themes. This is slowing down starting up my editor in my WSL and I noticed the same when my Vim installation was on a network share (possibly in conjunction with some anti-virus application). This is just annoying. Best, Christian -- Die neue A-Klasse soll jetzt serienmäßig mit einem Überrollbügel ausgerüstet werden. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20210107191737.GD2910256%40256bit.org.
