true | { sleep 1 ; read -rt0 ; echo $?; }
outputs 0. There can clearly be no data on the stdin of the second process in
the pipeline.
bash(1) has this to say about read -t:
"If timeout is 0, read returns immediately, without trying to read any data.
The exit status is 0 if input is availabl
Emily Seville wrote on Sun, Nov 21, 2021 at 01:40:08PM +1000:
> Bash version: GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
> OS version: Linux Mint 20.2 Cinnamon
>
> Hello! Why when I create *complete -C 'echo -e "aa\nab\n"' : *completion and
> try use it I obtain additional garbage i
Bash version: GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
OS version: Linux Mint 20.2 Cinnamon
Hello! Why when I create *complete -C 'echo -e "aa\nab\n"' : *completion
and try use it I obtain additional garbage in output instead of only *ab
ab* hints?
Date:Sat, 20 Nov 2021 15:19:33 -0500
From:Chet Ramey
Message-ID:
| Right. Purposeful.
There's a difference between done intentionally for pragmatic reasons,
and done intentionally because it is the right thing to do and people
should depend upon it remaining that
On 11/20/21 12:35 PM, Robert Elz wrote:
Date:Sat, 20 Nov 2021 11:33:37 -0500
From:Chet Ramey
Message-ID: <4addb789-50b6-12a5-7b8a-8a082abaa...@case.edu>
| I'm skeptical, but willing to be convinced. Bourne's shell allowed EOF to
| terminate all sorts of thi
Date:Sat, 20 Nov 2021 11:33:37 -0500
From:Chet Ramey
Message-ID: <4addb789-50b6-12a5-7b8a-8a082abaa...@case.edu>
| I'm skeptical, but willing to be convinced. Bourne's shell allowed EOF to
| terminate all sorts of things (quoted strings, command substitutions, her
On 11/19/21 9:18 AM, Robert Elz wrote:
illusory compat issues. I have no idea what inspired this initially, but
my guess would be a code bug no-one noticed.
I'm skeptical, but willing to be convinced. Bourne's shell allowed EOF to
terminate all sorts of things (quoted strings, command substit
