Re: bug report

On Fri, Apr 23, 2021 at 10:43 AM john wrote: > From: john > To: bug-bash@gnu.org > Subject: ls dumps bash > > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt

Re: broken pipe from func-output by changing network settings?

On Tue, Oct 17, 2017 at 1:37 PM, Ángel wrote: > bash converts < <( dd_need_io "$if" "$of" ...) into a read > from /dev/fd/62 in order to make readarray read file descriptor 62. > > Given that this the host OS doesn't provide them, the first thing I > would verify would be: is cygwin, as setup

Re: Error message garbage when parameter expansion used inside (()) and variable unset

On Mon, Apr 2, 2018 at 5:16 PM, PRussell wrote: > > echo 4B > ( set -x;var=5;var1=var; (( var1 == $var2 )) && echo yes || echo no ) > > > It appears that 3A and 4A evaluate to 0 because of the arithmetic context. > 3A echo's yes; 4A echo's no. > > The problem is what is happening with 3B and 4B

INT still propagating to child processes when trapped

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale'

Re: Reading from a file by using its FD returns its contents only once

On Sun, Dec 30, 2018 at 8:37 PM mike b wrote: > Configuration Information: > Machine: x86_64 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' > -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' > -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/sh

Re: Is it normal for `bash -s foo` not to make 1=foo available from ~/.bashrc?

On Mon, Mar 27, 2017 at 8:32 AM, Torka Noda wrote: > For any particular reason? > > Why are they not all made available anyway? with an alternative > array for the arguments sent to the commands fed to Bash stdin > with "-s", so we don't have to handle all possible arguments if > we just want the

Re: Infinite loop in bash glob matching

The '[:' may be messing with it, 'a[[:alpha:]:abm[]' should work. It won't match 'amm' because the range only matches a single character, you'd need 'a+([[:alpha:]:abm[])' On Tue, May 16, 2017 at 10:49 AM, Eduardo Bustamante wrote: > On Tue, May 16, 2017 at 2:48 AM, Zoltán Herczeg > wrote: > >