From 246404a44d14e733d275e20c32dcb756e5b88a0b Mon Sep 17 00:00:00 2001 From: Peter Stephenson Date: Fri, 12 Sep 2014 20:35:16 +0100 Subject: Add $functypestack special parameter in zsh/parameter --- Doc/Zsh/mod_parameter.yo | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) (limited to 'Doc') diff --git a/Doc/Zsh/mod_parameter.yo b/Doc/Zsh/mod_parameter.yo index 32d4796f7..c1571603c 100644 --- a/Doc/Zsh/mod_parameter.yo +++ b/Doc/Zsh/mod_parameter.yo @@ -201,7 +201,10 @@ The format of each element is var(filename)tt(:)var(lineno). For functions autoloaded from a file in native zsh format, where only the body of the function occurs in the file, or for files that have been executed by the tt(source) or `tt(.)' builtins, the trace information is -shown as var(filename)tt(:)var(0), since the entire file is the definition. +shown as var(filename)tt(:)var(0), since the entire file is the +definition. + +The most recent call is the first element in the array. Most users will be interested in the information in the tt(funcfiletrace) array instead. @@ -221,4 +224,13 @@ The format of each element is var(name)tt(:)var(lineno). Callers are also shown for sourced files; the caller is the point where the tt(source) or `tt(.)' command was executed. ) +vindex(functypestack) +item(tt(functypestack))( +This array corresponds element by element with tt(funcstack). +Each element contains `tt(source)' for a sourced file, `tt(function)' +for a function and `tt(eval)' for an tt(eval)'d expression. At the top +level of execution of a series of commands, tt($functypestack[1]) is +empty if the commands are being executed as a script, or one of the +previous strings if the commands are being executed as that type. +) enditem() -- cgit 1.4.1