From: Bart Schaefer <schaefer@brasslantern.com>
To: Oliver Kiddle <opk@zsh.org>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] declarednull: rename DECLARED to NULL
Date: Sat, 10 Apr 2021 15:35:12 -0700 [thread overview]
Message-ID: <CAH+w=7absqR0zCq_pXUHrenYrtK0pAEaNAh0u88mn3S1nFOkJA@mail.gmail.com> (raw)
In-Reply-To: <63964-1618091881.198315@P0pm.eEwl.WXLl>
On Sat, Apr 10, 2021 at 2:58 PM Oliver Kiddle <opk@zsh.org> wrote:
>
> I don't really have a strong opinion but would like to see the work
> finished off and pushed.
I did another forced-push on the declarednull branch after rebase on
master (though a couple of other master changes flowed in almost
immediately after that).
> never easy to name these things.
A problem with TYPESET_DOES_NOT_SET is that it leads to the
double-negative NO_TYPESET_DOES_NOT_SET, which isn't as bad as
NO_NO_whatever, but argues for an option that is treated as "on" for
the existing behavior. Bleah.
If I do add a separate option, do you think it's OK to combine that
with POSIX_BUILTINS for the tests in the (new) E03posix.ztst file?
Otherwise all the tests in that file will have to be repeated twice
(with and without the new option).
prev parent reply other threads:[~2021-04-10 22:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 22:13 Felipe Contreras
2021-01-03 1:18 ` Bart Schaefer
2021-01-03 2:38 ` Felipe Contreras
2021-01-03 18:26 ` Bart Schaefer
2021-01-04 6:17 ` Daniel Shahaf
2021-01-04 21:57 ` Bart Schaefer
2021-01-06 16:02 ` Daniel Shahaf
2021-01-06 17:33 ` Bart Schaefer
2021-01-07 15:48 ` Daniel Shahaf
2021-01-07 22:29 ` Bart Schaefer
2021-03-27 19:24 ` Lawrence Velázquez
2021-03-27 20:42 ` Bart Schaefer
2021-03-29 0:44 ` Oliver Kiddle
2021-04-10 18:56 ` Bart Schaefer
2021-04-10 21:58 ` Oliver Kiddle
2021-04-10 22:35 ` Bart Schaefer [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='CAH+w=7absqR0zCq_pXUHrenYrtK0pAEaNAh0u88mn3S1nFOkJA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=opk@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).