I've been running Vim with the HOME environment variable set for a couple
of weeks now and it's remained consistently fast to start up. As a test I
went back to unsetting $HOME and it went back to being very slow to start,
so there's definitely some combination of the way I've got vim set up (the
On Mon, 12 Sept 2022 at 15:32, Andrew Bernard wrote:
> ...
> static const char *required_env_vars[] = {
> #ifdef WIN32
>"HOMEDRIVE",
>"HOMEPATH",
> ...
nice.
> But if you are running in cygwin I would have thought that shell only
> uses a UNIX environment, so $HOME would be all that is
Looking at the source code for neovim (I'll check gvim later) I see the
following in a file called funcs.c that evaluates the environment
variables among other things:
/// According to comments in src/win/process.c of libuv, Windows has a few
/// "essential" environment variables.
static const
-- Original Message --
From: "jr"
To: vim_use@googlegroups.com
Sent: Monday, 12 Sep, 2022 At 15:09
Subject: Re: Gvim taking a minute or more to start
On Mon, 12 Sept 2022 at 14:26, A. S. Budden wrote:
...
Oooh, that was a good shot! Setting the HOME environment variable seems
to
On Mon, 12 Sept 2022 at 14:26, A. S. Budden wrote:
> ...
> Oooh, that was a good shot! Setting the HOME environment variable seems to
> work (again, I've only tested this on one machine so far; I'll try the other
> tomorrow). It doesn't seem to matter what it's set to: I tried
>
On Fri, 9 Sept 2022, 12:45 jr, wrote:
> 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
On Fri, 9 Sept 2022, 12:48 Andrew Bernard, wrote:
> Take a look at Windows Event Viewer. You may be able to glean something
> from that.
>
I can't see anything obvious, but then I don't really know what I'm looking
for.
> Do you have an antivirus program running?
>
As far as I know, only the
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
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
On Fri, 9 Sept 2022 at 12:06, A. S. Budden wrote:
> On Thu, 8 Sept 2022, 19:29 Gary Johnson, 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
On Thu, 8 Sept 2022, 19:29 Gary Johnson, wrote:
> 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
On Thu, 8 Sept 2022, 19:38 Tim Chase, wrote:
> On 2022-09-08 11:30, Gary Johnson wrote:
> > 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
>
On 2022-09-08 11:30, Gary Johnson wrote:
> 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
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
On Thu, 8 Sept 2022 at 17:33, 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
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
16 matches
Mail list logo
