zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: "Once-a-day" long delay before startup
Date: Sat, 20 Aug 2011 00:01:31 -0700	[thread overview]
Message-ID: <110820000131.ZM23095@torch.brasslantern.com> (raw)
In-Reply-To: <20110820004710.GA4085@andrew.cmu.edu>

On Aug 19,  8:47pm, gi1242+zsh@gmail.com wrote:
} Subject: Re: "Once-a-day" long delay before startup
}
} On Thu, Aug 18, 2011 at 09:05:58PM -0700, Bart Schaefer wrote:
} 
} > Refer to my earlier reply -- do as soon as possible during startup:
} > 
} >     unsetopt hashcmds hashdirs hashlistall
} 
} Indeed. Even with
} 
}     unsetopt hashcmds hashdirs
} 
} zsh starts quickly.

Yes, as I mentioned, hashlistall really only applies later, but there
is no point in leaving it set if the other two are unset.

} I'm not sure how this problem can be solved (if at all).

Why is the above not a solution?

I suppose you mean a solution that doesn't require you to change your
zshenv configuration.  One possibility is that we could declare the
hashcmds and hashdirs options to be obsolete, and no longer have them
on by default.  (I doubt they're necessary for non-interactive shells
in any event.)  Meanwhile ...

Here's a crude pass at a function set for caching the hash table.  It
writes the current value of $PATH as the first line of the file and
reads back that line to determine whether the file matches the path
in the current shell.  The store function fills the cache and writes
the file all in the background.  Improvements are possible.

emulate -R zsh -c '#
cachehash_valid() {
  local _typeset cachepath
  [[ -n $cachefile && -O $cachefile &&
     -r $cachefile && ! -w $cachefile ]] &&
  IFS="=" read _typeset cachepath < $cachefile &&
  [[ $cachepath == $PATH ]]
}
cachehash_store() {
  local cachefile=${ZDOTDIR:-$HOME}/.zcachehash
  { hash -f && umask 0277 &&
    { typeset -p PATH
      print "hash -r"
      hash -L } >| $cachefile-$$ &&
    command mv -f $cachefile-$$ $cachefile } &!
}
cachehash_load() {
  local cachefile=${ZDOTDIR:-$HOME}/.zcachehash
  cachehash_valid && source $cachefile
}
#'

Also, I just invented that idiom of '# ... #' for wrapping the argument
of "emulate zsh -c ..." but it seems like a good way to make obvious
the presence of the quotes.

-- 
Barton E. Schaefer


  reply	other threads:[~2011-08-20  7:02 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
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 [this message]
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=110820000131.ZM23095@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).