From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: "Once-a-day" long delay before startup
Date: Thu, 18 Aug 2011 21:05:58 -0700 [thread overview]
Message-ID: <110818210558.ZM20788@torch.brasslantern.com> (raw)
In-Reply-To: <20110819020336.GA21062@andrew.cmu.edu>
On Aug 18, 10:03pm, gi1242+zsh@gmail.com wrote:
}
} I've no idea why "which dircolors" takes such a long time on zsh (when
} the cache is cleared), and runs instantly on sh. I'd appreciate any
} help.
sh doesn't do command hashing, it re-searches the path every time.
Refer to my earlier reply -- do as soon as possible during startup:
unsetopt hashcmds hashdirs hashlistall
On my system "zsh -fc 'which ...'" takes about 40% as long with those
options unset as it does with them set.
Zsh is making the assumption that you'd prefer one big delay of a few
seconds at startup, to many tiny delays all the while the shell is
running. However, zsh's default options were determined in a time
when path searching was slow and those "tiny" delays were a lot less
tiny. Of course the tradeoff for getting your prompt sooner is that
you're going to have a delay the first time you attempt command
completion, because completion needs a filled hash table.
next prev parent reply other threads:[~2011-08-19 4:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 14:57 gi1242+zsh
2011-08-14 15:36 ` Vincent Lefevre
2011-08-14 17:32 ` Vincent Lefevre
2011-08-14 18:06 ` Bart Schaefer
2011-08-18 22:08 ` Piotr Karbowski
2011-08-19 2:03 ` gi1242+zsh
2011-08-19 4:05 ` Bart Schaefer [this message]
2011-08-19 9:08 ` Vincent Lefevre
2011-08-19 17:58 ` Bart Schaefer
2011-08-20 0:47 ` gi1242+zsh
2011-08-20 7:01 ` Bart Schaefer
2011-08-19 3:52 ` Bart Schaefer
2011-08-19 8:36 ` Vincent Lefevre
2011-08-19 9:05 ` Piotr Karbowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=110818210558.ZM20788@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).