Re: ${p+\"$p\"}

2019-01-22 Thread Robert Elz
Date:Tue, 22 Jan 2019 20:23:50 -0600 From:Eric Blake Message-ID: <77d63ba1-64ba-c0a8-7d32-9d8cc3289...@redhat.com> | Rather, POSIX says the behavior is undefined, That's what it is going to say, when Issue 8 is published, some years into the future (how many, anyon

Re: ${p+\"$p\"}

2019-01-22 Thread Eric Blake
On 1/22/19 6:36 PM, 積丹尼 Dan Jacobson wrote: > OK so bash is right and dash is wrong? So I should file a dash bug? Rather, POSIX says the behavior is undefined, so both shells are right, and you cannot portably use " inside ${p+...} when in a double-quoted context (such as a heredoc). For more det

Re: ${p+\"$p\"}

2019-01-22 Thread 積丹尼 Dan Jacobson
OK so bash is right and dash is wrong? So I should file a dash bug?

Re: UUID as Array Keys strangely not possible

2019-01-22 Thread Chet Ramey
On 1/22/19 3:32 PM, Robert White wrote: > Howdy, > > The following cannot work because, for some reason, the array subscript > parser insists on doing math on array indices even when the array is > associative instead of numeric > > typeset -A UUID_TABLE > ... > UUID_TABLE+=( [${SOME_UUID}]=${SOM

UUID as Array Keys strangely not possible

2019-01-22 Thread Robert White
Howdy, The following cannot work because, for some reason, the array subscript parser insists on doing math on array indices even when the array is associative instead of numeric typeset -A UUID_TABLE ... UUID_TABLE+=( [${SOME_UUID}]=${SOME_VALUE} ) ... some_command ${UUID_TABLE[${SOME_UUID}]

Re: loadable cat bug?

2019-01-22 Thread Ángel
On 2019-01-21 at 20:03 -0600, Peng Yu wrote: > When I use the loadable cat, I may get the following error. The input > is a fifo in this specific case. > > cat: cannot open /tmp/tmp.VXkbqFlPtH: Interrupted system call > > So far, I can not make a minimal script to demonstrate the problem. > But i

Re: Where is GLOBAL_COMMAND?

2019-01-22 Thread Eric Blake
On 1/22/19 2:37 PM, Peng Yu wrote: >> That's a documentation convention - the all-caps in the docstring calls >> your attention to the need to search case-insensitively for the actual >> variable, while spelling it case-sensitively would make it blend into >> the sentence and make it harder to real

Re: Where is GLOBAL_COMMAND?

2019-01-22 Thread Peng Yu
> That's a documentation convention - the all-caps in the docstring calls > your attention to the need to search case-insensitively for the actual > variable, while spelling it case-sensitively would make it blend into > the sentence and make it harder to realize that the sentence is indeed > point

Re: Readline bug?

2019-01-22 Thread Rob Foehl
On Tue, 22 Jan 2019, Greg Bell wrote: On bash 4.3.48 (Ubuntu 16.04), \C-e doesn't work to move me to the end of line when in vi command mode. This is specific to bash, and has been the case for as long as I can remember. I thought I'd reported it, but maybe not... As a workaround, in .bash

Re: Where is GLOBAL_COMMAND?

2019-01-22 Thread Chet Ramey
On 1/22/19 12:32 AM, Peng Yu wrote: > Hi, > > GLOBAL_COMMAND is mentioned as a global variable. But I don't find it. > Is it renamed to something else? grep global_command *.? -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrate

Re: Where is GLOBAL_COMMAND?

2019-01-22 Thread Eric Blake
On 1/22/19 7:47 AM, Peng Yu wrote: >> grep global_command *.? > > GLOBAL_COMMAND is uppercase. But the actual variable name > global_command is in lowercase. That's a documentation convention - the all-caps in the docstring calls your attention to the need to search case-insensitively for the act

Bash-5.0 Official Patch 1

2019-01-22 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 5.0 Patch-ID: bash50-001 Bug-Reported-by:a...@freakout.de Bug-Reference-ID: <201901082050.x08koshs006...@bongo.freakout.de> Bug-Reference-URL: http://lists.gnu.o

Bash-5.0 Official Patch 2

2019-01-22 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 5.0 Patch-ID: bash50-002 Bug-Reported-by:Ante Peric Bug-Reference-ID: Bug-Reference-URL: http://lists.gnu.org/archive/html/bug-bash/2019-01/msg00095.html Bug-

Re: Installing bash with rpath

2019-01-22 Thread Chet Ramey
On 1/20/19 7:47 PM, Mohammad Akhlaghi wrote: > On 1/21/19 12:25 AM, Chet Ramey wrote: >> Isn't there a linker option you can supply, possibly as part of LDFLAGS, >> to embed that into the bash binary? > > I pass `-Wl,-rpath-link=$instdir/lib' to LDFLAGS. It sets RPATH properly on > all the program

Re: Where is GLOBAL_COMMAND?

2019-01-22 Thread Peng Yu
> grep global_command *.? GLOBAL_COMMAND is uppercase. But the actual variable name global_command is in lowercase. I think that GLOBAL_COMMAND should be changed to global_command in the comment. -- Regards, Peng

Re: Readline bug?

2019-01-22 Thread Chet Ramey
On 1/21/19 10:01 PM, Greg Bell wrote: > > Hi Chet et al, > > On bash 4.3.48 (Ubuntu 16.04), \C-e doesn't work to move me to the end of > line when in vi command mode. Thanks for the report. This has been there forever. The default readline vi command-mode keymap has ^E bound to switch to emacs e