From: "Pádraig Brady" <P@draigBrady.com>
To: r n <neemro@gmail.com>, 67160@debbugs.gnu.org
Subject: bug#67160: defect with linux expr command on chromebook build 118
Date: Tue, 14 Nov 2023 12:05:52 +0000 [thread overview]
Message-ID: <0b3f804c-311e-5653-f971-ecfd5bb7e40e@draigBrady.com> (raw)
In-Reply-To: <CAPs7DeCjC7LKb7C1nLE=TBhQvkGpDTW6zU470VsU2fD+hdK+FQ@mail.gmail.com>
tag 67160 notabug
close 67160
stop
On 14/11/2023 06:42, r n wrote:
> I have a lenovo slim 3 chromebook with linux version 5.15.130-etc and when
> expr encounter an asterisk for multiplying args, it return a syntax error
> unexpected argument 'code 1'. All other arithmetic operators are correctly
> interpreted. Please let me know if you need more information to reproduce
> the issue.
This sounds like the '*' is not appropriately quoted,
and the shell is expanding it.
For details see:
https://www.gnu.org/software/coreutils/faq/coreutils-faq.html#expr-2-_002a-3-does-not-work
thanks,
Pádraig
prev parent reply other threads:[~2023-11-14 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 6:42 bug#67160: defect with linux expr command on chromebook build 118 r n
2023-11-14 12:05 ` Pádraig Brady [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
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0b3f804c-311e-5653-f971-ecfd5bb7e40e@draigBrady.com \
--to=p@draigbrady.com \
--cc=67160@debbugs.gnu.org \
--cc=neemro@gmail.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).