On Thu, Feb 26, 2015 at 2:40 AM, Milo H. Fields
wrote:
> Greetings,
>
> I noticed that the 'bang-hash' behavior seems to have changed somewhere
> between bash version 4.1.17 and 4.3.33.
>
>
>
> e.g. for the script 'jnk' containing:
>
> echo "plain: !#"
>
> echo " parens: ${!#}"
>
>
>
> bash 4.3.
On Wed, Feb 25, 2015 at 07:40:07PM -0500, Milo H. Fields wrote:
> echo " parens: ${!#}"
> bash 4.1.17:
>
> $ sh jnk arg1 arg2
>
> plain: !#
>
> parents: arg2
Can't say I've ever seen this syntax before. It looks like you are
trying to get the last argument. The syntax I've seen for getting
On 2/25/15 7:40 PM, Milo H. Fields wrote:
> Greetings,
>
> I noticed that the ‘bang-hash’ behavior seems to have changed somewhere
> between bash version 4.1.17 and 4.3.33.
>
>
>
> e.g. for the script ‘jnk’ containing:
>
> echo "plain: !#"
> echo " parens: ${!#}"
It changed for Posix mode b
On 2/26/15 1:01 PM, Chet Ramey wrote:
> On 2/26/15 8:20 AM, Corentin Peuvrel wrote:
>> Hello,
>>
>> I found a bug in bash-4.1 (CentOS 6) that was fixed (at least) in bash-4.3
>> (Fedora 21).
>>
>> $ foo=aXb ; echo "$BASH_VERSION : ${foo/X/\'}"
>> 4.3.33(1)-release : a'b
>>
>> $ foo=aXb ; echo "$BAS
On 2/26/15 2:37 PM, ad...@ptc.com wrote:
> Bash Version: 4.2
> Patch Level: 47
> Release Status: release
>
> Description:
> A bash function containing the syntax "files=( !(PAT) )" fails to parse
> in a sub-shell when imported from the environment (to which it was exported
> by the pare
