typeset docs flow Re: [PATCH] typeset: set $? on incidental error

[Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>]

Daniel Shahaf wrote on Fri, Jan 29, 2016 at 09:18:34 +0000:
> diff --git a/Doc/Zsh/builtins.yo b/Doc/Zsh/builtins.yo
> index fb630a7..6e3d146 100644
> --- a/Doc/Zsh/builtins.yo
> +++ b/Doc/Zsh/builtins.yo
> @@ -1826,6 +1826,23 @@ reserved word interface for tt(typeset) may cause problems with the
>  output of `tt(typeset -p)', which assumes the reserved word interface is
>  available in order to restore array and associative array values.
>  
> +Unlike parameter assignment statements, tt(typeset)'s exit status on an
> +assignment that involves a command substitution does not reflect the exit
> +status of the command substitution.  Therefore, to test for an error in
> +a command substitution, separate the declaration of the parameter from its
> +initialization:
> +
> +example(# WRONG
> +typeset var1=$(exit 1) || echo "Trouble with var1"
> +
> +# RIGHT
> +typeset var1 && var1=$(exit 1) || echo "Trouble with var1"
> +)
> +
> +To initialize a parameter var(param) to a command output and mark it readonly,
> +use tt(typeset -r )var(param) or tt(readonly )var(param) after the parameter
> +assignment statement.
> +

The following paragraph (the context lines of the patch) is the
continuation of the text about var(name) that precedes the segment about
the reserved word syntax.

The fix is probably to move the whole reserved words chunk to right
before the startitem() of the control flags?  I'd fix that but I'm short
on time at the moment and don't want to do a rush job of it.

Daniel

>  If the shell option tt(TYPESET_SILENT) is not set, for each remaining
>  var(name) that refers to a parameter that is already set, the name and
>  value of the parameter are printed in the form of an assignment.