From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [PATCH] [long] typeset doesn't report tied parameters (and related issues)
Date: Mon, 8 Oct 2018 08:54:58 -0700 [thread overview]
Message-ID: <CAH+w=7ZPEYRa2_z4s3wbxVeHY+U3L72mQm0JTsph1vy-1wViKA@mail.gmail.com> (raw)
In-Reply-To: <20181008152406eucas1p1660f190ddb4bcd4c0131c4c84492a9f2~bq3vkNlyg2997729977eucas1p1I@eucas1p1.samsung.com>
On Mon, Oct 8, 2018 at 8:24 AM Peter Stephenson
<p.stephenson@samsung.com> wrote:
>
> Hmm, I'm guessing all the B02 failures are all down to being re-run from
> V10?
No, they're coming from the first pass through B02. Succeeds for me
on MacOS, but on CentOS 6.10 it fails:
Test ./B02typeset.ztst failed: bad status 1, expected 0 from:
function {
local -rax zsh_exported_readonly_array=(2)
local -rAx zsh_exported_readonly_hash=(3 3)
local -rx zsh_exported_readonly_scalar=1
print zsh:
export -p | grep zsh_exported_readonly
readonly -p | grep zsh_exported_readonly
print sh:
emulate -L sh
export -p | grep zsh_exported_readonly
readonly -p | grep zsh_exported_readonly
print still asking for arrays:
export -ap | grep zsh_exported_readonly
readonly -ap | grep zsh_exported_readonly
}
Was testing: no array/hash in POSIX export/readonly -p
There is no other useful output, even with ZTST_VERBOSE.
next prev parent reply other threads:[~2018-10-08 15:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 21:05 [PATCH] typeset -p doesn't report -U (unique) attribute Stephane Chazelas
2018-09-25 16:41 ` Daniel Shahaf
2018-10-07 13:35 ` [PATCH] [long] typeset doesn't report tied parameters (and related issues) Stephane Chazelas
2018-10-08 9:05 ` Peter Stephenson
[not found] ` <CACeGjnUhNqca7jLAR0KKSxobzDd+xXdAe4BeUeRpxu2CTp_zkA@mail.gmail.com>
2018-10-08 14:10 ` Peter Stephenson
2018-10-08 14:28 ` Daniel Shahaf
2018-10-08 15:24 ` Peter Stephenson
2018-10-08 15:49 ` Daniel Shahaf
2018-10-08 15:57 ` Bart Schaefer
2018-10-08 16:06 ` Daniel Shahaf
2018-10-08 16:52 ` Bart Schaefer
2018-10-08 16:58 ` Peter Stephenson
2018-10-08 16:02 ` Daniel Shahaf
2018-10-08 16:19 ` Peter Stephenson
2018-10-08 16:43 ` Peter Stephenson
2018-10-08 16:58 ` Daniel Shahaf
2018-10-08 17:14 ` Bart Schaefer
2018-10-08 19:39 ` Stephane Chazelas
2018-10-09 9:02 ` Peter Stephenson
[not found] ` <1539075745.1499.2.camel@samsung.com>
2018-10-09 9:44 ` Peter Stephenson
2018-10-09 16:52 ` Bart Schaefer
2018-10-09 23:40 ` Vin Shelton
2018-10-08 15:54 ` Bart Schaefer [this message]
2018-10-08 16:40 ` Bart Schaefer
2018-10-09 10:59 ` local read-only variables (Was:[PATCH] [long] typeset doesn't report tied parameters (and related issues)) Stephane Chazelas
2018-10-11 9:45 ` [PATCH] [long] typeset doesn't report tied parameters (and related issues) Oliver Kiddle
2018-10-11 12:46 ` 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='CAH+w=7ZPEYRa2_z4s3wbxVeHY+U3L72mQm0JTsph1vy-1wViKA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=p.stephenson@samsung.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).