On 2019-11-02 at 07:56 +0800, 積丹尼 Dan Jacobson wrote:
> $ mapping/taipower/pole2tm
> bash: mapping/taipower/pole2tm: No such file or directory
>
> Must be a bash bug! Proof:
> $ ls -l mapping/taipower/pole2tm
> -rwxr-xr-x 1 jidanni jidanni 11290 2012-06-19 mapping/taipower/pole2tm
>
> But wait,
On 11/13/19 10:59 AM, Shaun Crampton wrote:
> But the commands in the subshell execute inside a different shell
> execution context so they shouldn't have
> their own set -e context (Section 2.12)?
>
> I don't see where the spec says that the subshell has to inherit the
> and/or list-ness of the
>
On 11/13/19 10:59 AM, Andrew Church wrote:
"The -e setting shall be ignored when executing the compound list following
the while, until, if, or elif reserved word, a pipeline beginning with the
! reserved word, or any command of an AND-OR list other than the last."
(from
https://pubs.opengroup.o
On 11/13/19 10:59 AM, Shaun Crampton wrote:
But the commands in the subshell execute inside a different shell
execution context so they shouldn't have
their own set -e context (Section 2.12)?
Why? That section says the only thing that changes in the subshell
environment is signal dispositions.
Thanks for the explanation. I didn't know any of these
>"The -e setting shall be ignored when executing the compound list following
>the while, until, if, or elif reserved word, a pipeline beginning with the
>! reserved word, or any command of an AND-OR list other than the last."
>
>(from
>https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_
But the commands in the subshell execute inside a different shell
execution context so they shouldn't have
their own set -e context (Section 2.12)?
I don't see where the spec says that the subshell has to inherit the
and/or list-ness of the
parent context. Section 2.12 doesn't mention that as bei
On 11/13/19 5:24 AM, Shaun Crampton wrote:
Bash Version: 5.0
Patch Level: 3
Release Status: release
Description:
I was trying to get a function to return early if a command
fails by putting
the body of the function in a subshell and using set -e inside
the subshell.
If I
On 11/8/19 4:50 PM, Oğuz wrote:
v=foo
echo ${v#[[:"lower":]]}
should print oo, but it prints foo instead. This is reproducible on bash
4.4
Plus
case foo in (*[![:"lower":]]*) echo bar; esac
prints bar, while
The idea is that at this point in command processing, quote removal hasn't
been p
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2
-fdebug-prefix-map=/build/bash-LQgi2O/bash-5.0=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wno-parentheses -Wno-format-security
uname out
On 11/12/19 9:15 AM, p.debru...@unilogic.nl wrote:
Bash Version: 4.4
Patch Level: 23
Release Status: release
Description:
The loadable sleep function seems to exit almost immediately
in some specific cases.
It's getting interrupted by SIGCHLD. It's fixed in bash-5.0 by blockin
11 matches
Mail list logo
