zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Zsh hackers list <zsh-workers@zsh.org>
Cc: "Lawrence Velázquez" <larryv@zsh.org>
Subject: Re: RFC PATCH: Sketch at :@ subscripting
Date: Tue, 13 Apr 2021 11:54:10 +0000	[thread overview]
Message-ID: <20210413115410.GG6819@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <CAH+w=7arhEQnyN2ixKBGPoX8NoRrzErTQfPgBpnLd_AFpZQvtw@mail.gmail.com>

Bart Schaefer wrote on Sat, Apr 10, 2021 at 14:59:28 -0700:
> On Sat, Apr 10, 2021 at 1:39 PM Lawrence Velázquez <larryv@zsh.org> wrote:
> >
> > > Could someone add that as an XFail test (one with the 'F' flag)?
> 
> This OK?

+1.  The expectations are minimal, so the test will start to XPass as
soon as zsh's behaviour changes.  If the behaviour has changed because
the bug was fixed, we can extend the test's expectations then.

I'll only suggest to add this thread's X-Seq to the ztst file somewhere,
for ease of reference.

Thanks,

Daniel

> diff --git a/Test/D06subscript.ztst b/Test/D06subscript.ztst
> index c1a8d79cf..4225c543c 100644
> --- a/Test/D06subscript.ztst
> +++ b/Test/D06subscript.ztst
> @@ -289,3 +289,8 @@ F:Regression test for workers/42297
>  >14 24
>  >b b
>  >b?rbaz foob?r
> +
> +  i=1,3
> +  [[ ${a[$i]} = ${a[i]} ]]
> +0f:Math evaluation of commas in array subscripts
> +F:In math, (($i)) should be the same as ((i)).



  reply	other threads:[~2021-04-13 11:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18 13:18 Mikael Magnusson
2020-12-19  9:13 ` Stephane Chazelas
2021-03-27 20:27   ` Bart Schaefer
2021-04-03 19:48     ` Lawrence Velázquez
2021-04-04 17:30       ` Daniel Shahaf
2021-04-10 20:38         ` Lawrence Velázquez
2021-04-10 21:59           ` Bart Schaefer
2021-04-13 11:54             ` Daniel Shahaf [this message]
2021-04-13 21:25               ` Bart Schaefer
2021-03-27 19:41 ` Lawrence Velázquez

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=20210413115410.GG6819@tarpaulin.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=larryv@zsh.org \
    --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).