4579.000 030.000 030.000: sourcing $VIM\_gvimrc
42416.000 37840.000: starting GUI
026.000 001.000: init highlight
32606.000 000.000 000.000: sourcing C:\vim\runtime\ftoff.vim
38738.000 000.000 000.000: sourcing C:\vim\runtime\ftplugin\text.vim
88937.000 047.000 047.000: sourcing C:\vim\vimfiles\bundle\TagHighlight\autoload\TagHighlight\ReadTypes.vim
8484.000 000.000 000.000: sourcing C:\vim\runtime\ftplugin\text.vim
20153.000 034.000 034.000: sourcing C:\vim\vimfiles\bundle\TagHighlight\autoload\TagHighlight\ReadTypes.vim
45722.000 000.000 000.000: sourcing C:\vim\vimfiles\bundle\TagHighlight\autoload\TagHighlight\Debug.vim
From: vim...@googlegroups.com
<vim...@googlegroups.com> On Behalf Of
A. S. Budden
Sent: Thursday, September 8, 2022 9:44 AM
> On my work PCs, gvim seems to take an incredibly long time to start up, sometimes as much as 90 seconds.
Is this a PC that is attached to a network that has IT governing HOMEDRIVE?
> In timecost1.txt, we have:
4579.000 030.000 030.000: sourcing $VIM\_gvimrc
42416.000 37840.000: starting GUI
Reason being, 5 seconds was to open $VIM\_gvimrc (which, on my computer is %HOMEDRIVE%\_vimrc). If you have latency when accessing %HOMEDRIVE% perhaps that is your issue?
I had a similar issue and remapped my %HOMEDRIVE% (in Windows 10) to a local directory by creating a shortcut within Startup with:
C:\Windows\System32\subst.exe P: "A:\home"
My vim now starts up nicely -- though, I no longer have a network attached HOMEDRIVE.
0.02USD,
Andy
>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.
On my work machine, gvim with -u NONE takes 100 milliseconds to start.
It takes 600 milliseconds to start with my current vimrc. I use several,
but perhaps not a very large amount, of plugins. I interpret this to
mean that it might be reasonable for startuptime to multiply by a factor
of 6 or so when loading several plugins?
>Can anyone suggest what I can do to try to diagnose the cause of the
>delay? The only thought I've had is to delete plugins from the bundle
>directory one-by-one until it starts quickly but that seems a rather
>haphazard approach.
I'll note that a binary search for relevant plugins is probably faster
than a one-by-one search. I'm sorry I wasn't more helpful.
From: vim...@googlegroups.com <vim...@googlegroups.com> On Behalf Of A. S. Budden
Sent: Thursday, September 8, 2022 9:44 AM
> On my work PCs, gvim seems to take an incredibly long time to start up, sometimes as much as 90 seconds.
Is this a PC that is attached to a network that has IT governing HOMEDRIVE?
> In timecost1.txt, we have:
4579.000 030.000 030.000: sourcing $VIM\_gvimrc
42416.000 37840.000: starting GUI
Reason being, 5 seconds was to open $VIM\_gvimrc (which, on my computer is %HOMEDRIVE%\_vimrc). If you have latency when accessing %HOMEDRIVE% perhaps that is your issue?
On Thu, 8 Sept 2022, 19:29 Gary Johnson, <gary...@spocom.com> wrote:
On 2022-09-08, David Lowry-Duda wrote:So if I run Windows gvim from a cygwin terminal it starts quickly but if I run it from a windows command prompt or from windows explorer, it takes ages. I've tried this lots of times & it seems to be repeatable (I even created 10 instances of gvim in a loop and they all appeared straightaway).
I tried removing the HOME environment variable from cygwin (it's not set to anything in the Windows system, whereas it's set to /home/al in cygwin) and ran the command again from the cygwin terminal and it took a long time to start. I reset HOME to /home/al and it still took a long time to start! Opening a new cygwin terminal resulted in a quick start again. This is really weird!
Take a look at Windows Event Viewer. You may be able to glean something from that.
Do you have an antivirus program running?
--
--
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+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/eb996918-4d2a-4f6d-80d8-5f08a9d3d3ean%40googlegroups.com.
hi,
On Fri, 9 Sept 2022 at 12:39, A. S. Budden wrote:
> ...
>> I tried removing the HOME environment variable from cygwin (it's not set to anything in the Windows system, whereas it's set to /home/al in cygwin) and ran the command again from the cygwin terminal and it took a long time to start. I reset HOME to /home/al and it still took a long time to start! Opening a new cygwin terminal resulted in a quick start again. This is really weird!
(shot in the dark, have no MS Windows) what happens if you set a HOME
variable under Windows?
It seems it is to do with their view of a file system. It's divided into HOMEDRIVE and HOMEPATH. It wd seem reasonable to insert a concatenation of these as HOME. I hesitate to offer a command, or where it sd go.
Chris Willis
--
--
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+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAM-dBgqFM4gXqkH8q3j96rvEtRTv5h%3Dd59O0w0FSu4vWh-bhuA%40mail.gmail.com.