From: Peter Stephenson <firstname.lastname@example.org>
To: Zsh hackers list <email@example.com>
Subject: Re: [PATCH] Named reference typos & misc.
Date: Tue, 14 Feb 2023 16:36:49 +0000 (GMT) [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 14/02/2023 16:14 Bart Schaefer <email@example.com> wrote:
> On Tue, Feb 14, 2023 at 6:47 AM Peter Stephenson
> <firstname.lastname@example.org> wrote:
> > I need the following to make the tests pass --- else no error message.
> I get a passed test with or without the "unsetopt typeset_to_unset".
> Is there some way this could be platform-dependent?
Was wondering; this is pretty old, Ubuntu 16.04, x86_64. I don't have
anything bang up to date but I've got some alternatives I can try.
Here's a minimal case:
zsh -fc 'setopt typeset_to_unset
typeset -n ref
for ref in one; do
No error message; sticking an "un" at the start makes it appear.
I kept the loop in the function to avoid a (correct) additional warning
message setting the global variable ref in the loop. I don't know if
setting ref in a for loop should actually elide that message, which
is a completely separate issue.
next prev parent reply other threads:[~2023-02-14 16:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 2:08 Bart Schaefer
2023-02-14 14:46 ` Peter Stephenson
2023-02-14 16:14 ` Bart Schaefer
2023-02-14 16:36 ` Peter Stephenson [this message]
2023-02-14 20:00 ` Bart Schaefer
2023-02-15 1:39 ` Bart Schaefer
2023-02-16 15:29 ` zmodload (-u?) changing options (was Re: [PATCH] Named reference typos & misc.) Bart Schaefer
2023-02-16 15:52 ` Peter Stephenson
2023-02-16 18:17 ` Bart Schaefer
2023-02-16 19:28 ` Bart Schaefer
2023-02-16 23:10 ` Bart Schaefer
2023-02-21 11:47 ` Peter Stephenson
2023-02-21 12:11 ` Peter Stephenson
2023-02-21 15:57 ` Bart Schaefer
2023-02-15 10:12 ` [PATCH] Named reference typos & misc Peter Stephenson
2023-02-15 10:36 ` Peter Stephenson
2023-02-15 14:58 ` Bart Schaefer
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).