Date:Mon, 16 Nov 2020 22:59:39 -0500
From:wor...@alum.mit.edu (Dale R. Worley)
Message-ID: <87ft58ws44@hobgoblin.ariadne.com>
| Although I must say, I can't recall off the top of my head what Un*x
| utility best capitalizes the first letter of a string.
sed
On Mon, Nov 16, 2020 at 10:36:48PM -0800, L A Walsh wrote:
> or (to reproduce error):
> an_alias='res=() t=""
>for ci in "${!foo[@]}"; do \
Nice detective work there. I can confirm this in Debian's bash 5.0.3:
unicorn:~$ alias foo='a=() b=""
> for i in 1; do echo hi; done'
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2
-fdebug-prefix-map=/build/bash-2bxm7h/bash-5.0=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall$
uname output: Linux zebulon
On Tue, Nov 17, 2020 at 09:35:35AM +0100, Pierre Colombier via Bug reports for
the GNU Bourne Again SHell wrote:
> I'm not sure this is actually a bug since dash act the same way but
> it's quite unexpected for the average user
Agreed! The behavior of set -e is extremely surprising, and
$ alias x='a=()
foo
echo $a'
$ x
foo
$ declare -p a
declare -a a=([0]="foo")
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On 17/11/2020 at 16:00, Ilkka Virta wrote:
Now, perhaps that could use a note explicitly saying this also means
subshells, even though they may
have set -e in effect independently of the main shell.
The part explaining subshells (3.7.3 Command Execution Environment) could
perhaps also use a
Greg Wooledge:
> The behavior of set -e is extremely surprising, and people should
> stop expecting it to make intuitive sense. The best way to avoid being
> surprised by it is to stop using it altogether.
Has it ever been considered to add something like 'shopt -s
composable_compound'? Roughly
On Tue, Nov 17, 2020 at 4:07 PM Pierre Colombier via Bug reports for the
GNU Bourne Again SHell wrote:
> #2
> pierre@zebulon: ~ $ (set -e ; echo A ; false ; echo B ) && echo C.$?
> #3
> pierre@zebulon: ~ $ bash -c 'set -e ; echo A ; false ; echo B ' && echo
> C.$?
If it's not a bug, I
On 11/17/20 7:56 AM, Greg Wooledge wrote:
On Mon, Nov 16, 2020 at 10:36:48PM -0800, L A Walsh wrote:
or (to reproduce error):
an_alias='res=() t=""
for ci in "${!foo[@]}"; do \
Nice detective work there. I can confirm this in Debian's bash 5.0.3:
unicorn:~$ alias foo='a=()
Anyone to look why this is no longer connected to the bug-bash@gnu.org ML?
--
Lea Gris
Rusty Bird writes:
>> The behavior of set -e is extremely surprising [...]
> Has it ever been considered to add something like 'shopt -s
> composable_compound'? Roughly meaning "execution and exit status of a
> compound command are not changed by surrounding context (in the sense
> of logical
11 matches
Mail list logo
