On Mon, Feb 27, 2012 at 6:44 AM, Davide Baldini
wrote:
> On 02/27/12 05:04, DJ Mills wrote:
>> Think of regular here-doc (with an unquoted word) as being treated the
>> same way as a double-quoted string
>
> Thank you Mills, of course I can understand it _now_, after having hit
> the problem, but
On Sun, Feb 26, 2012 at 10:11 PM, Dan Douglas wrote:
> On Monday, February 27, 2012 04:03:34 AM Davide Baldini wrote:
>> Is this expected? Standing at the debian's man bash, variables inside
>> 'here document' are supposed to expand with no special exceptions
>> and undergo word
On 02/27/12 05:04, DJ Mills wrote:
> Think of regular here-doc (with an unquoted word) as being treated the
> same way as a double-quoted string
Thank you Mills, of course I can understand it _now_, after having hit
the problem, but my point is different: the description of a program's
details sho
On Monday, February 27, 2012 04:03:34 AM Davide Baldini wrote:
> Is this expected? Standing at the debian's man bash, variables inside
> 'here document' are supposed to expand with no special exceptions
> and undergo word splitting and pathname expansion.
"If word is unquoted, al
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='ba
On 2/26/12 6:06 AM, Dan Douglas wrote:
> I just tested a bunch of permutations. I was a bit surprised to see this one
> fail:
You shouldn't have been. The entire function definition, including the
additional embedded function definition, is parsed before any of it is
executed.
>
> f()
>
On 2/25/12 3:42 PM, Davide Baldini wrote:
> Bash Version: 4.1
> Patch Level: 5
> Release Status: release
>
> Description:
> A 'test.sh` script file composed exclusively of the following text
> fails execution:
> #!/bin/bash
> (
> shopt
On 02/22/2012 08:59 PM, Eric Blake wrote:
> On 02/22/2012 12:55 PM, Chet Ramey wrote:
>> On 2/21/12 5:07 PM, John Kearney wrote:
>>>
>>> Initial code for testing \u functionality.
>>
>> Thanks; this is really good work. In the limited testing I've
>> done, ja_JP.SHIFT_JIS is rare and C.UTF-8 doe
I updated that wiki page
Hopefully its clearer now.
http://mywiki.wooledge.org/glob#extglob
On 02/26/2012 12:06 PM, Dan Douglas wrote:
> On Saturday, February 25, 2012 09:42:29 PM Davide Baldini wrote:
>
>> Description: A 'test.sh` script file composed exclusively of the
>> following text fails
On Saturday, February 25, 2012 09:42:29 PM Davide Baldini wrote:
> Description:
> A 'test.sh` script file composed exclusively of the following text
> fails execution:
> #!/bin/bash
> (
> shopt -s extglob
> echo !(
On 02/25/2012 09:42 PM, Davide Baldini wrote:
> 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_VEN
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='ba
12 matches
Mail list logo