On Sunday, February 19, 2012 04:25:46 PM Chet Ramey wrote:
> On 2/17/12 6:22 PM, Dan Douglas wrote:
> > My favorite is probably the parser ignoring any valid redirection syntax
> > with the special command substitutions.
> >
> > ~ $ { echo "$({} >
> > hi
>
> Bash does the sa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can somebody explain to me what u32tochar is trying to do?
It seems like dangerous code?
from the context i'm guessing it trying to make a hail mary pass at
converting utf-32 to mb (not utf-8 mb)
int
u32tochar (x, s)
unsigned long c;
char
On 2/18/12 4:51 AM, John Kearney wrote:
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/17/12 6:22 PM, Dan Douglas wrote:
> My favorite is probably the parser ignoring any valid redirection syntax with
> the special command substitutions.
>
> ~ $ { echo "$({} hi
Bash does the same thing as ksh93 here, though
On 2/17/12 2:51 PM, Mike Frysinger wrote:
> can't tell if this is a bug or a feature.
>
> FOO= BAR=bar
> : ${FOO:=${BAR}
> echo $FOO
>
> i'd expect an error, or FOO to contain those excess braces. instead, FOO is
> just "bar".
Neither. That's just how p
When compiling bash-4.2.20 with CFLAGS +=-Werror=format-security,
there is a warning easy to fix :
print_cmd.c: In function 'indent':
print_cmd.c:1397: warning: format not a string literal and no format
arguments
Debian has a patch for this since bash-4.1. I haven't seen the patch
reported so here
