On Sunday, February 9, 2025, Martin D Kealey
wrote:
>
> (Arguing about printf potentially being an external command is pointless
>
It is an external command when you use it with xargs. GNU coreutils ships a
printf implementation compatible with bash.
Rest of your reply is drivel as usual
--
O
Date:Sun, 9 Feb 2025 08:52:07 -0500
From:Greg Wooledge
Message-ID: <20250209135207.gn29...@wooledge.org>
| Oh, that must be another 2024 change.
As my earlier correction indicated, it didn't happen.
It turns out that all the *ash shells (bash, yash, and all derive
Date:Sun, 09 Feb 2025 12:30:33 +0700
From:Robert Elz
Message-ID: <16760.1739079...@jacaranda.noi.kre.to>
| read -- but doesn't need to be as read -p is in the standard.
I was sure that had been added, but as usual when I am relying
on memory I was wrong, -p isn't i
On Sun, Feb 09, 2025 at 12:30:33 +0700, Robert Elz wrote:
> | and "read -p" for the prompt.
>
> which could be just a printf without a trailing \n before the
> read -- but doesn't need to be as read -p is in the standard.
Oh, that must be another 2024 change. The manpages-posix package I've
go
On Sat, 8 Feb 2025, 17:48 Robert Elz, wrote:
>
> | and if the correspondence with strtol() is to be taken at face value,
> | this would likewise imply that empty string is a valid representation
> for
> | zero, since strtol() reports that it has converted the entire string in
> | that cas
