From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
<zsh-workers@sunsite.auc.dk>
Subject: PATCH: RE: Is this statement correct?
Date: Tue, 19 Sep 2000 12:00:56 +0400 [thread overview]
Message-ID: <000401c0220f$bd609090$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1000919071851.ZM30493@candle.brasslantern.com>
>
> The order of $fpath takes precedence over the newness of the files. It
> doesn't search for the newest thing anywhere in $fpath; it checks for
> the newest one of any two otherwise-equivalent sources of the function.
>
If you agree with my english, I'll commit it to avoid more confusion.
-andrej
Index: Doc/Zsh/contrib.yo
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Zsh/contrib.yo,v
retrieving revision 1.6
diff -u -r1.6 contrib.yo
--- Doc/Zsh/contrib.yo 2000/09/15 15:32:25 1.6
+++ Doc/Zsh/contrib.yo 2000/09/19 07:59:18
@@ -81,7 +81,9 @@
digests compiled with the tt(zcompile) builtin are frequently out of date
with respect to the function source files. This is not usually a problem,
because zsh always looks for the newest file when loading a function, but
-it may cause slower shell startup and function loading.
+it may cause slower shell startup and function loading. Also, if digest
+file is explicitly used as element of tt(fpath), zsh won't check if any
+of its source files was changed.
The tt(zrecompile) autoloadable function, found in tt(Functions/Misc), can
be used to keep function digests up to date.
prev parent reply other threads:[~2000-09-19 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-07 11:41 Sven Wischnowsky
2000-09-19 5:50 ` Andrej Borsenkow
2000-09-19 7:18 ` Bart Schaefer
2000-09-19 8:00 ` Andrej Borsenkow [this message]
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='000401c0220f$bd609090$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/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).