2022年8月3日(水) 5:57 Chet Ramey :
> On 8/2/22 4:18 PM, Robert E. Griffith wrote:
> > Is there a reason why POSIX would want the return behavior to of function
> > down the stack to behave differently when in a trap? Seems strange to me.
>
> I don't remember if Koichi ever opened up a bug with the Aust
https://getyarn.io/yarn-clip/cea30edb-a7a6-465b-bc51-3d53d9281447
It was worth the wait:)
--BobG
On 8/2/22 16:57, Chet Ramey wrote:
On 8/2/22 4:18 PM, Robert E. Griffith wrote:
The first (getyarn...) link renders as a blank page for me. What it
is supposed to be?
https://getyarn.io/yarn-
On 8/2/22 4:18 PM, Robert E. Griffith wrote:
The first (getyarn...) link renders as a blank page for me. What it is
supposed to be?
https://getyarn.io/yarn-clip/cea30edb-a7a6-465b-bc51-3d53d9281447
Is there a reason why POSIX would want the return behavior to of function
down the stack to
Oh darn, I have been writing bash scripts for a long time and have never
found a novel bug. I was hoping this would be my first:)
The first (getyarn...) link renders as a blank page for me. What it is
supposed to be?
Is there a reason why POSIX would want the return behavior to of
function d
On 8/2/22 3:38 PM, Robert E. Griffith wrote:
> Is it known behavior that return without a parameter will not set the exit
> code from the last command when called from the EXIT trap?
https://getyarn.io/_nuxt/f66cb012eec875e1f9262fd77ecdf31e.svg
https://lists.gnu.org/archive/html/bug-bash/2020-04/
Is it known behavior that return without a parameter will not set the
exit code from the last command when called from the EXIT trap?
$ cat -n exitReturnBug.sh
1 #!/usr/bin/bash
2 function shouldReturnFalse() {
3 false
4
