Re: Man Page: Confusing wording

2018-04-02 Thread Greg Wooledge
On Sat, Mar 31, 2018 at 05:00:51PM +0200, Lars Krueger wrote: >The line > >Of these list operators, && and || have equal precedence, followed >by ; and &, which have equal precedence. > >in the man page is rather confusing. I had to refresh my bison and >check parser.y to

Re: Loop within trap handling

2018-04-02 Thread Chet Ramey
On 3/28/18 10:02 AM, wer...@suse.de wrote: > Bash Version: 4.4 > Patch Level: 19 > Release Status: release > > Description: > A user reports a problem with example code included. By using the > the code shown below and doing Ctrl-C twice the code hangs within > a SIGINT loop if

Re: [BUG] ERR trap triggered twice when using 'command'

2018-04-02 Thread Nick Chambers
On 4/1/18, 5:54 AM, "bug-bash on behalf of Martijn Dekker" wrote: $ bash -c 'trap "echo WHOA" ERR; command false' WHOA WHOA Expected output: just one WHOA (as on *ksh, zsh) Thanks, - M. Please use the bashbug tool to submit the bug, so those that look

Re: [BUG] ERR trap triggered twice when using 'command'

2018-04-02 Thread Nick Chambers
On 4/1/18, 5:54 AM, "bug-bash on behalf of Martijn Dekker" wrote: $ bash -c 'trap "echo WHOA" ERR; command false' WHOA WHOA Expected output: just one WHOA (as on *ksh, zsh) Thanks, - M. While you should still use the bashbug tool, I’m not sure if this

Re: [BUG] ERR trap triggered twice when using 'command'

2018-04-02 Thread Greg Wooledge
On Mon, Apr 02, 2018 at 02:35:28PM +, Nick Chambers wrote: > On 4/1/18, 5:54 AM, "bug-bash on behalf of Martijn Dekker" > mart...@inlv.org> wrote: > > $ bash -c 'trap "echo WHOA" ERR; command false' > WHOA > WHOA > > Expected output: just one WHOA (as on *ksh, zsh) >

Re: [BUG] ERR trap triggered twice when using 'command'

2018-04-02 Thread Martijn Dekker
Op 02-04-18 om 16:47 schreef Nick Chambers: You should still be providing this information :). How else would you expect people to help you. I'm not looking for help. I'm here to report the bugs in bash that I find, and occasionally to help fix them. That's what this list is for. > Ni

Re: Error: conflicting types for ‘sbrk’

2018-04-02 Thread Larissa Braz
Dear Eduardo, 2018-03-22 11:36 GMT-03:00 Eduardo A. Bustamante López : > On Wed, Mar 21, 2018 at 11:07:45AM -0300, Larissa Braz wrote: > > Hi, > > > > I found the following compilation error: > > > > xmalloc.c:51:14: error: conflicting types for ‘sbrk’ > > extern char *sbrk(); > >

Re: command_not_found_handle strange behaviour

2018-04-02 Thread Chet Ramey
On 3/29/18 12:08 PM, Eduardo A. Bustamante López wrote: > On Wed, Mar 28, 2018 at 06:42:21PM +0300, Кириллов Дима wrote: > [...] >> Bash Version: 4.4 >> Patch Level: 19 >> Release Status: release >> >> Description: >> I can't understand why read works without subshell before it, >> but with s

Re: [BUG] ERR trap triggered twice when using 'command'

2018-04-02 Thread Chet Ramey
On 4/1/18 6:54 AM, Martijn Dekker wrote: > $ bash -c 'trap "echo WHOA" ERR; command false' > WHOA > WHOA > > Expected output: just one WHOA (as on *ksh, zsh) Thanks for the report. This clearly falls under this clause "In every other respect, if command_name is not the name of a function, the ef

Re: A question about bash change for efficiency speedups in multibyte locales

2018-04-02 Thread Chet Ramey
On 3/29/18 9:57 PM, yangyajing wrote: > Hello,  I recently did lsb-test-core on ubuntu 16.04. There is a test > that can be successful in bash 4.1 but fails in bash 4.3. > > The test comment is :  bash tp10.sh. > > The content of tp10.sh is :   echo [[:xdigit:]] [[:hyphen:]]. > > And this test s

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

2018-04-02 Thread PRussell
Section 6.5 Shell Arithmetic says, "Within an expression, shell variables may also be referenced by name without using the parameter expansion syntax. A shell variable that is null or unset evaluates to 0 when referenced by name without using the parameter expansion syntax." - http://www.gnu.org/s