On 2022-09-08, David Lowry-Duda wrote:
> >I'm pretty sure it's something about my configuration / plugins /
> >something (gvim -u NONE -U NONE takes about 5 seconds), but I'm
> >really struggling to diagnose the issue / work out which plugin is
> >responsible. I've got a lot of plugins that I've added over the
> >years and I probably don't need all of them, but it would be nice
> >to which is the culprit rather than just start culling them at
> >random.
>
> Five seconds feels like a *really* long time for base gvim. I don't
> use Windows, so perhaps my scale is off. But this feels like an
> eternity.
If it takes 5 seconds to start gvim with no plugins, especially when
using a local SSD, something is very wrong someplace. I just ran
this command on my Windows 10 PC (with a hard drive) from a Cygwin
prompt so that I could measure the time:
$ time /cygdrive/c/Program\ Files/Vim/vim90/gvim -f -c scriptnames -cq
real 0m0.216s
user 0m0.000s
sys 0m0.000s
I had it execute :scriptnames just so it would have something
to do before immediately quitting. And that's with loading all
my plugins. With "-N -u NONE -i NONE", the real time dropped
to 0.17 s.
I suspect that whatever is causing that 5-second startup time is
contributing to the read times of every file that gvim opens.
So, while 5 seconds is better than 30, solving that 5-second issue
may solve the rest.
Unfortunately, I don't anything about diagnosing issues with Windows
or security programs.
Regards,
Gary
--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20220908183042.GK6741%40phoenix.
Thursday, September 8, 2022
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment