Re: Man Page: Confusing wording

2018-04-10 Thread Tadeus Prastowo
On Tue, Apr 10, 2018 at 1:32 AM, L A Walsh wrote: > > How about the below, suggested wording replacing these 2 paragraphs: > >A list is a sequence of one or more pipelines separated by one of the >operators ;, &, &&, or ||, and optionally terminated by one of ;, &, or >. > >Of th

[BUG] RETURN trap with -o functrace: infinite recursion on 'eval return'

2018-04-10 Thread Martijn Dekker
$ bash -o functrace -c 'fn() { eval "return"; }; trap "fn" RETURN; fn' Result: segfault due to infinite recursion. __ Even apart from this bug with 'eval return', the effect of '-o functrace' is a bit strange: $ bash -o functrace -c 'fn() { printf foo; fn2; }; fn2() { printf

Re: [PATCH] READLINE_POINT with multibyte locales

2018-04-10 Thread Koichi Murase
(I'm sorry. I directly replied to Chet's e-mail address by mistake. Let me send the reply again to the mailing list.) Hi Chet, Thank you for your explanation. 2018-04-10 0:26 GMT+09:00 Chet Ramey : > Because the underlying readline variable that it controls, rl_point, is > kept in bytes -- an in

Re: proper bash configure behavior when /dev/stdin is present, /dev/{,self/}fd are not?

2018-04-10 Thread Chet Ramey
On 4/9/18 7:20 PM, Brian Carnes wrote: > Chet, > >   Please find attached patches for bash 4.3.x and 4.4 for full > functionality under QNX 6.x and 7.0 Thanks for the patch. I'm curious why you chose to patch configure, when it will just be overwritten the next time it's built from configure.ac.

Re: proper bash configure behavior when /dev/stdin is present, /dev/{,self/}fd are not?

2018-04-10 Thread Brian Carnes
Chet, > I'm curious why you chose to patch configure Ha! For the simple reason that we don't have autoconf and friends in the native embedded QNX environment. Nor do we have it on the cross-compiling build server (but we could more easily add it there, that's at least not QNX). Here's a rev

Following symlinks in globstar (part 2)

2018-04-10 Thread Murukesh Mohanan
This has come up in the past, and was somewhat resolved (< http://lists.gnu.org/archive/html/bug-bash/2014-03/msg00097.html>), but bash's behaviour is still a but surprising IMHO. While globstar doesn't descend further into symlinks, symlinked directories are selected as a candidate for matches to