On Wed, 9 Apr 2025 at 15:40, Chet Ramey <chet.ra...@case.edu> wrote:
>
> On 4/9/25 9:31 AM, Dan Shelton wrote:
> > On Wed, 9 Apr 2025 at 15:16, Chet Ramey <chet.ra...@case.edu> wrote:
> >>
> >> On 4/9/25 2:09 AM, Cedric Blancher wrote:
> >>> Good morning!
> >>>
> >>> Could bash please support x=${<space>cmd;} alongside x=$(cmd)?
> >>
> >> I implemented it back in 2023 and it will be in bash-5.3.
> >>
> >> There was quite a long discussion about it:
> >>
> >> https://lists.gnu.org/archive/html/bug-bash/2023-05/msg00042.html
> >
> > I don't like the x=${| ,,,} form. HP/UX had a crazy /bin/sh extension
> > for some time to read pipe input for the "..." cmd, but it was so
> > buggy that it was infamous with support staff.
> >
> > Docs should clarify that this is NOT the HP/UX madness
>
> Why not read the documentation describing it first?
Clarification:
bash and ksh93 x=${ cmd;} is great!!!
What is not great is the cmd | x=${|cmd;} extension in HP/UX which
randomly hung or crashed /bin/sh in a way to make the tty locked and
unuseable. People who remember the HP/UX /bin/sh extension will suffer
from PTSD if they see that syntax, esp university admins where
students used this as "sport" to take down machines. HP fortunately
removed their HP/UX /bin/sh extension very fast.
Dan
--
Dan Shelton - Cluster Specialist Win/Lin/Bsd
