From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: behavior of test true -a \( ! -a \)
Date: Sat, 23 Mar 2024 14:48:36 -0700 [thread overview]
Message-ID: <CAH+w=7bAB+cx-f_qBMKoec=Hdyj_s_pRUeiE8K8wyr_ig1rDeQ@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7a+P6d_D3BxiO7hqPji9LbduYcu53ZFOSbg8DkL4QK8og@mail.gmail.com>
On Thu, Mar 21, 2024 at 10:39 AM Bart Schaefer
<schaefer@brasslantern.com> wrote:
>
> I'm guessing the change is from commit 2afa556d8 (workers/31696).
That commit includes this comment:
+ /*
+ * In "test" compatibility mode, "! -a ..." and "! -o ..."
+ * are treated as "[string] [and] ..." and "[string] [or] ...".
+ */
The way this is tested was changed first at commit cb596a55
(workers/35306) and again at commit daa208e9 (workers/49269) to end up
with this:
if (!(n_testargs > 2 && (check_cond(*testargs, "a") ||
check_cond(*testargs, "o"))))
So this means that in the original example:
% test true -a \( ! -a \) ; echo $?
test: argument expected
The closing \) is being treated as the string argument of [ ! -a \) ]
rather than as a match for the opening \(.
Which you can see by:
% test \( ! -a \) \)
% echo $?
0
% test \( ! -a \) \) \)
test: too many arguments
I'd therefore argue that it's actually
% test \( ! -a \)
that is wrong: It should be complaining of a missing close paren,
rather than magically reverting to treating "!" as "not" (and also
"-a" as a plain string). It's entirely dependent on the count of
arguments rather than on treating parens as tokens.
next prev parent reply other threads:[~2024-03-23 21:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 10:07 Vincent Lefevre
2024-03-21 10:28 ` Peter Stephenson
2024-03-21 11:04 ` Vincent Lefevre
2024-03-21 11:29 ` Peter Stephenson
2024-03-21 12:18 ` Vincent Lefevre
2024-03-21 12:25 ` Peter Stephenson
2024-03-21 19:06 ` Bart Schaefer
2024-03-22 5:02 ` Bart Schaefer
2024-03-25 16:38 ` Peter Stephenson
2024-03-25 17:36 ` Bart Schaefer
2024-04-03 13:59 ` Vincent Lefevre
2024-03-21 17:39 ` Bart Schaefer
2024-03-23 21:48 ` Bart Schaefer [this message]
2024-03-23 22:20 ` Vincent Lefevre
2024-03-23 22:41 ` Bart Schaefer
2024-03-23 23:33 ` Lawrence Velázquez
2024-03-24 0:14 ` Bart Schaefer
2024-03-24 2:52 ` Lawrence Velázquez
2024-03-25 10:23 ` Vincent Lefevre
2024-03-25 15:21 ` Bart Schaefer
2024-03-25 17:33 ` Vincent Lefevre
2024-03-25 17:43 ` Bart Schaefer
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=7bAB+cx-f_qBMKoec=Hdyj_s_pRUeiE8K8wyr_ig1rDeQ@mail.gmail.com' \
--to=schaefer@brasslantern.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).