From: Bart Schaefer <schaefer@brasslantern.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Bug with unset variables
Date: Fri, 27 Nov 2020 16:24:56 -0800 [thread overview]
Message-ID: <CAH+w=7awR=pODg+mcHKvssPyWPPhDeOb-TMG3B336bfeLOKf=w@mail.gmail.com> (raw)
In-Reply-To: <564f91d0-fb87-4472-a566-a5e261ef8ae7@www.fastmail.com>
[Apparently when I tried to go look at another message, a blank reply
got sent off.]
On Fri, Nov 27, 2020 at 3:38 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> The best way to move forward would be to write a patch against the Test/
> directory that specifies the proposed behaviour. Use the "f" flag so
> all newly-added tests will run, rather than just the first.
There are existing tests that specifically check for the current
behavior, so it's not as if this were simply overlooked.
To write the proposed new test cases, we need to decide (this list may
not be all-inclusive):
whether this is going to be attached to an option (and which one, now
that Oliver to at least some extent disagrees with KSH_TYPESET) or is
controlled by emulation mode;
what happens to "setopt NO_UNSET";
what "typeset -p" outputs following "unset".;
what happens when each (any) of the EFHLRTZilu options are passed to typeset;
whether we are OK with the implications of the foregoing when the -x
option is also present.
next prev parent reply other threads:[~2020-11-28 0:25 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 15:57 Felipe Contreras
2020-11-11 16:13 ` Roman Perepelitsa
2020-11-11 16:56 ` Felipe Contreras
2020-11-11 17:02 ` Roman Perepelitsa
2020-11-11 18:03 ` Felipe Contreras
2020-11-11 18:16 ` Roman Perepelitsa
2020-11-11 20:42 ` Felipe Contreras
2020-11-12 0:20 ` Mikael Magnusson
2020-11-12 1:10 ` Felipe Contreras
2020-11-12 8:45 ` Roman Perepelitsa
2020-11-12 10:47 ` Peter Stephenson
2020-11-12 18:48 ` Bart Schaefer
2020-11-12 19:49 ` Felipe Contreras
2020-11-12 18:46 ` Felipe Contreras
2020-11-12 19:10 ` Roman Perepelitsa
2020-11-12 21:08 ` Felipe Contreras
2020-11-13 8:51 ` Roman Perepelitsa
2020-11-14 0:52 ` Felipe Contreras
2020-11-14 5:41 ` Roman Perepelitsa
2020-11-16 19:41 ` Felipe Contreras
2020-11-16 20:22 ` Roman Perepelitsa
2020-11-17 20:28 ` Felipe Contreras
2020-11-18 22:45 ` Daniel Shahaf
2020-11-22 1:20 ` Felipe Contreras
2020-11-23 4:00 ` Daniel Shahaf
2020-11-23 6:18 ` Felipe Contreras
2020-11-19 2:59 ` Bart Schaefer
2020-11-22 1:50 ` Felipe Contreras
2020-11-17 20:54 ` Bart Schaefer
2020-11-22 1:49 ` Felipe Contreras
2020-11-23 6:48 ` Bart Schaefer
2020-11-23 7:26 ` Felipe Contreras
2020-11-23 20:26 ` Bart Schaefer
2020-11-23 23:39 ` Felipe Contreras
2020-11-24 0:52 ` Bart Schaefer
2020-11-25 8:46 ` Felipe Contreras
2020-11-27 15:44 ` Daniel Shahaf
2020-11-27 20:49 ` Felipe Contreras
2020-11-27 20:59 ` Daniel Shahaf
2020-11-27 21:33 ` Bart Schaefer
2020-11-27 23:37 ` Daniel Shahaf
2020-11-27 23:45 ` Bart Schaefer
2020-11-28 0:24 ` Bart Schaefer [this message]
2020-11-28 7:32 ` Bart Schaefer
2020-11-28 12:05 ` Felipe Contreras
2020-11-12 19:26 ` Bart Schaefer
2020-11-12 21:48 ` Felipe Contreras
2020-11-13 22:17 ` Bart Schaefer
2020-11-14 0:58 ` Felipe Contreras
2020-11-11 18:36 ` Bart Schaefer
2020-11-11 21:08 ` Felipe Contreras
2020-11-11 17:02 ` Peter Stephenson
2020-11-11 18:05 ` Felipe Contreras
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=7awR=pODg+mcHKvssPyWPPhDeOb-TMG3B336bfeLOKf=w@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=d.s@daniel.shahaf.name \
--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).