From: Mikael Magnusson <mikachu@gmail.com>
To: zsh-workers@sunsite.dk
Subject: Re: Clarify zshaddhistory doc?
Date: Wed, 18 Feb 2009 18:15:00 +0100 [thread overview]
Message-ID: <237967ef0902180915i563440d7u43f95c8390cf82a6@mail.gmail.com> (raw)
In-Reply-To: <200902181709.n1IH9DsQ019474@news01.csr.com>
2009/2/18 Peter Stephenson <pws@csr.com>:
> Index: Doc/Zsh/func.yo
> ===================================================================
> RCS file: /cvsroot/zsh/zsh/Doc/Zsh/func.yo,v
> retrieving revision 1.23
> diff -u -r1.23 func.yo
> --- Doc/Zsh/func.yo 5 Sep 2008 09:05:23 -0000 1.23
> +++ Doc/Zsh/func.yo 18 Feb 2009 17:07:35 -0000
> @@ -189,19 +189,23 @@
> sect(Special Functions)
> Certain functions, if defined, have special meaning to the shell.
>
> -In the case of tt(chpwd), tt(periodic), tt(precmd) and tt(preexec) it is
> -possible to define an array that has the same name with `tt(_functions)'
> -appended. Any element in such an array is taken as the name of a function
> -to execute; it is executed in the same context and with the same arguments
> -as the basic function. For example, if tt($chpwd_functions) is an array
> -containing the values `tt(mychpwd)', `tt(chpwd_save_dirstack)', then the
> -shell attempts to execute the functions `tt(chpwd)', `tt(mychpwd)' and
> +subsect(Hook Functions)
> +findex(functions, hook)
> +findex(hook functions)
> +
> +For the functions below, it is possible to define an array that has the
> +same name as the function with `tt(_functions)' appended. Any element in
> +such an array is taken as the name of a function to execute; it is executed
> +in the same context and with the same arguments as the basic function. For
> +example, if tt($chpwd_functions) is an array containing the values
> +`tt(mychpwd)', `tt(chpwd_save_dirstack)', then the shell attempts to
> +execute the functions `tt(chpwd)', `tt(mychpwd)' and
> `tt(chpwd_save_dirstack)', in that order. Any function that does not exist
> is silently ignored. A function found by this mechanism is referred to
> -elsewhere as a `hook function'. An error in any function causes
> -subsequent functions not to be run. Note further that an error
> -in a tt(precmd) hook causes an immediately following tt(periodic)
> -function not to run (thought it may run at the next opportunity).
> +elsewhere as a `hook function'. An error in any function causes subsequent
> +functions not to be run. Note further that an error in a tt(precmd) hook
> +causes an immediately following tt(periodic) function not to run (thought
> +it may run at the next opportunity).
Driveby typo fix, thought -> though.
--
Mikael Magnusson
next prev parent reply other threads:[~2009-02-18 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 16:57 Bart Schaefer
2009-02-18 17:09 ` Peter Stephenson
2009-02-18 17:15 ` Mikael Magnusson [this message]
2009-02-18 18:39 ` Bart Schaefer
2009-02-19 10:02 ` Peter Stephenson
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=237967ef0902180915i563440d7u43f95c8390cf82a6@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=zsh-workers@sunsite.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).