Re: Another little patch I would like to put upstream

2016-12-07 Thread Mike Frysinger
On 07 Dec 2016 19:09, Chet Ramey wrote: > On 12/5/16 11:01 PM, Mike Frysinger wrote: > > using ^ as an anchor doesn't seem that much better than % > > Ultimately, autoconf is the right way to do this. sure, you could add bashbug to AC_OUTPUT and adapt all the vars to be AC_SUBST. i assume you'll

Re: Another little patch I would like to put upstream

2016-12-07 Thread Chet Ramey
On 12/5/16 11:01 PM, Mike Frysinger wrote: > using ^ as an anchor doesn't seem that much better than % Ultimately, autoconf is the right way to do this. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CW

Re: Tests are using fixed path /tmp/x

2016-12-07 Thread Chet Ramey
On 12/7/16 10:39 AM, Vladimir Marek wrote: > Hi, > > I'm sure you already love me :) Here's little something I hit recently. Yes, there are several instances of using filenames in /tmp instead of something in $TMPDIR that need fixing. Chet -- ``The lyf so short, the craft so long to lerne.''

Re: bash variable expansion ${var:+"..."} in here-document removes double quotes

2016-12-07 Thread Chet Ramey
On 12/7/16 7:31 AM, andreas.l...@innovative-navigation.de wrote: > Bash Version: 4.4 > Patch Level: 0 > Release Status: release > > Description: > > Bash removes double quotes (but not single quotes) when doing variable > expansion with ${parameter:+word} (Use Alternate Value), in a here-documen

Re: Problem outputting a quote in a variable expansion which is in a here doc

2016-12-07 Thread Chet Ramey
On 12/6/16 7:56 PM, Daniel Einspanjer wrote: > Bash Version: 4.4 > Patch Level: 5 > Release Status: release > > Description: > Tested on OSX as well as Ubuntu GNU/Linux 14.4 and Debian Jessie 8 > Tested with Bash 4.3 and 4.4 > > When trying to output a string from a variable expansio

Tests are using fixed path /tmp/x

2016-12-07 Thread Vladimir Marek
Hi, I'm sure you already love me :) Here's little something I hit recently. Cheers -- Vlad # The test new-exp1 used /tmp/x which is too common file to and might be # already present. The test then fails with: # # run-new-exp # ... # 171,172c171 # < ./new-exp1.sub: line 8: /tmp/x: Permiss

Re: SHOBJ_STATUS problem

2016-12-07 Thread Chet Ramey
On 12/7/16 8:40 AM, Vladimir Marek wrote: >>> And last nit I have stumbled upon ... >> >> Thanks, I fixed this one in early October as the result of >> >> http://lists.gnu.org/archive/html/bug-bash/2016-10/msg4.html > > But it's not part of bash-4.4 patchlevel 5, so do you keep your fixes > so

Re: Problem outputting a quote in a variable expansion which is in a here doc

2016-12-07 Thread Daniel Einspanjer
Awesome, thanks for this tip! On Wed, Dec 7, 2016 at 8:44 AM Greg Wooledge wrote: > On Wed, Dec 07, 2016 at 12:56:00AM +, Daniel Einspanjer wrote: > > echo The desired output is: > > echo "var = \"test test\"" > > imadev:~$ q=\" > imadev:~$ var="a variable" > imadev:~$ cat < > ${var:+var = $

Re: Problem outputting a quote in a variable expansion which is in a here doc

2016-12-07 Thread Greg Wooledge
On Wed, Dec 07, 2016 at 12:56:00AM +, Daniel Einspanjer wrote: > echo The desired output is: > echo "var = \"test test\"" imadev:~$ q=\" imadev:~$ var="a variable" imadev:~$ cat < ${var:+var = $q$var$q} > EOF var = "a variable" imadev:~$ echo "$BASH_VERSION" 4.4.0(1)-release Putting literal q

Re: SHOBJ_STATUS problem

2016-12-07 Thread Vladimir Marek
> > And last nit I have stumbled upon ... > > Thanks, I fixed this one in early October as the result of > > http://lists.gnu.org/archive/html/bug-bash/2016-10/msg4.html But it's not part of bash-4.4 patchlevel 5, so do you keep your fixes somewhere else? Looking around there is git reposito

Re: SHOBJ_STATUS problem

2016-12-07 Thread Chet Ramey
On 12/7/16 7:41 AM, Vladimir Marek wrote: > Hi, > > And last nit I have stumbled upon ... Thanks, I fixed this one in early October as the result of http://lists.gnu.org/archive/html/bug-bash/2016-10/msg4.html Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer

bash variable expansion ${var:+"..."} in here-document removes double quotes

2016-12-07 Thread andreas . luik
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/local/share

SHOBJ_STATUS problem

2016-12-07 Thread Vladimir Marek
Hi, And last nit I have stumbled upon ... Cheers -- Vlad # If $ac_cv_func_dlopen is not 'yes' a bit earlier, SHOBJ_LIBS remains # undefiled. Later during 'make install' stage, examples/loadables/Makefile # calls install-$(SHOBJ_STATUS), and since the target 'install-' is undefined, # mak

Re: bash tests failing when compiled with --enable-xpg-echo-default=yes

2016-12-07 Thread Vladimir Marek
> >>> And second patch we use because of xpg-echo. Would it have sense to have > >>> it included, or maybe stop the tests completely instead? > >> > >> You could just have turned off the xpg_echo option instead of going through > >> a convoluted test (which just emulates `shopt -q') to determine wh

Problem outputting a quote in a variable expansion which is in a here doc

2016-12-07 Thread Daniel Einspanjer
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: darwin15.6.0 Compiler: clang Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='darwin15.6.0' -DCONF_MACHTYPE='x86_64-apple-darwin15.6.0' -DCONF_VENDOR='apple' -DLOCALEDIR='/usr/local/

Re: Another little patch I would like to put upstream

2016-12-07 Thread Vladimir Marek
> using ^ as an anchor doesn't seem that much better than % > > autoconf uses & and |, but they tend to do it for vars where it's > unlikely those will show up (like path vars) > > how about something like: > @s=$$(printf '\001'); \ > sed -e "s$$s!MACHINE!$$s$(Machine)$$s" ... Good i