Re: exit-on-error (set -e) option and command after "if" not found

2011-06-22 Thread Eric Blake
On 06/22/2011 06:51 AM, Dmitry Bolshakov wrote: > Hi > > set -e > if nosuchcommand | grep blabla > then > echo ERROR: blabla was found > exit 1 > fi > echo it was unexpected for me, I thougt this line should not be echoed Not a bug; this last echo is supposed to happen. The documentation for

Calling Bash with /S

2011-06-22 Thread sweinberger
Hi All, I am calling bash from dmake. The make file initiates the call to bash as follows: /bin/bash /S /c "" The command to execute is between the double quotes. For instance In Make File: @ls -l ./SomeDir/* Bash Command /bin/bash /S /c "ls -l ./SomeDir/*" The /S from what I see enables r

printf treats arguments of "%c" not as expected

2011-06-22 Thread Yunfeng Wang
Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash

exit-on-error (set -e) option and command after "if" not found

2011-06-22 Thread Dmitry Bolshakov
Hi set -e if nosuchcommand | grep blabla then echo ERROR: blabla was found exit 1 fi echo it was unexpected for me, I thougt this line should not be echoed (bash 4.1.10(4)-release) -- With best regards Dmitry Bolshakov

Re: printf treats arguments of "%c" not as expected

2011-06-22 Thread Jonathan Nieder
Hi, Yunfeng Wang wrote: > $ printf %c 65 66 67 > 666 > > The expected output is ABC, i.e. characters with ASCII code of 65 66 67 I believe the current behavior is correct. POSIX (XCU.4.printf) sayeth[*]: 11. The argument to the 'c' conversion specifier can be a string