From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: dg1727 <dg1727@protonmail.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Patch: Doc: clarify effect of KSH_ARRAYS on subscript (I)
Date: Sun, 12 Apr 2020 01:32:37 +0000 [thread overview]
Message-ID: <20200412013237.46fd081a@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <iUg6Q8HfsmZJeHxtvQXRUea0qOugvQz8Wb5SY6qpKifTq8_rzc9hWOZFa18cbGEAXdhrg3eHCyZWf3W7FubOk6yOsHVHDkT-l9TEIDEosS8=@protonmail.com>
dg1727 wrote on Tue, 07 Apr 2020 23:20 +0000:
> Hello,
>
> Following is a Git diff of a proposed update to the documentation.
>
> In future, if I have a small item like this to suggest, I intend to try to combine it with other small items so as not to make too much mailing-list traffic. (I make no promises about this.)
>
> This first minor update is just to try out the process.
>
>
> Doc: clarify effect of KSH_ARRAYS on subscript (I)
>
> diff --git a/Doc/Zsh/params.yo b/Doc/Zsh/params.yo
> index 8daf33d5e..8682ec448 100644
> --- a/Doc/Zsh/params.yo
> +++ b/Doc/Zsh/params.yo
> @@ -397,7 +397,9 @@ associative array.
> item(tt(I))(
> Like `tt(i)', but gives the index of the last match, or all possible
> matching keys in an associative array. On failure substitutes 0, or
> -the empty string for an associative array. This flag is best when
> +the empty string for an associative array. If option tt(KSH_ARRAYS) is in
> +effect and no match is found, the result is indistinguishable from the case
> +when the first element of the array matches. This flag is best when
> testing for values or keys that do not exist.
> )
> item(tt(k))(
>
>
> Many thanks.
Thanks for the patch! I've applied it with minor changes. (I've been
AFK all week or I'd have done so sooner)
Cheers,
Daniel
prev parent reply other threads:[~2020-04-12 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 23:20 dg1727
2020-04-12 1:32 ` Daniel Shahaf [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=20200412013237.46fd081a@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=dg1727@protonmail.com \
--cc=zsh-workers@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).