Re: error message for missing fi is not helpful

2018-09-12 Thread L A Walsh
On 9/12/2018 6:35 AM, Chet Ramey wrote: On 9/12/18 5:17 AM, Manuel Reiter wrote: Bash Version: 4.4 Patch Level: 12 Release Status: release ++ Description: When an if statement is not terminated by a fi, bash's error message is not helpful in locating the problem. This is tough to

Re: error message for missing fi is not helpful

2018-09-12 Thread Chet Ramey
On 9/12/18 5:17 AM, Manuel Reiter wrote: > Bash Version: 4.4 > Patch Level: 12 > Release Status: release > > ++ Description: > > When an if statement is not terminated by a fi, bash's error message is > not helpful in locating the problem. This is tough to do in a bison-generated parser. If som

error message for missing fi is not helpful

2018-09-12 Thread Manuel Reiter
++ 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-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPAC

[PATCH] decode_signal: allow all sane forms of SIGRTMIN+n

2018-09-12 Thread Rasmus Villemoes
I have a program I'd like to send SIGRTMIN+20, because that's the spelling used in its documentation. Currently, bash only accepts the symbolic names in the signal_names array, meaning I'd have to spell it SIGRTMAX-10 on linux. One workaround is of course to use kill -n $(($(kill -l SIGRTMIN) +