Hi,
Bash doesn't seem to provide a handy way to perform search-and-replace
on strings in a case-insensitive manner.
The parameter expansion "${parameter/pattern/string}" is not influenced
by the shell options "nocaseglob" and "nocasematch", at least in Bash
version 4.2.37. Is this intended?
Configuration Information [Manually filled]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: //
uname output: Linux debianBunker 2.6.26-pentium4 #11 Fri Jul 20 10:03:38 CEST
2012 i686 GNU/Linux
Machine Type: i486-pc-linux-gnu
Bash Version: 4.2.0(5)-release (i686-pc-linux-gnu)
Descr
On 06/03/12 17:01, Geir Hauge wrote:
> 2012/6/3 Davide Baldini :
>> Description:
>> In the following test script I run an elementary coprocess to which the
>> echo built-in, run in background, attaches its standard-output:
>>
>>#!/bin/bash
>># TEST 1
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -O2 -march='i486' (plus the flags added by Makefile)
uname output: Linux debianBunker 2.6.26-2-686 #1 SMP Wed Sep 21 04:35:47
UTC 2011 i686 GNU/Linux
Machine Type: i486-pc-linux-gnu
Bash Version: 4.2.0(5)-release
Patch Level: 5
Release
On 02/17/12 20:51, Mike Frysinger wrote:
> FOO= BAR=bar
> : ${FOO:=${BAR}
> echo $FOO
Why should this be a bug? Your second line performs a parameter
expansion, all the remaining characters are joint into the token and
passed to ':'.
No bug.
On 02/26/12 12:41, John Kearney wrote:
> I updated that wiki page
> Hopefully its clearer now.
> http://mywiki.wooledge.org/glob#extglob
Valuable information. I wonder if some of it should be included in the
user manual, at least to point out some possible misbehaviours one
wouldn't expect.
On 02/27/12 04:11, Dan Douglas wrote:
> "If word is unquoted, all lines of the here-document are subjected to
> parameter expansion, command substitution, and arithmetic expansion."
>
> No pathname expansion.
That section of manual doesn't specifically include word splitting nor
pathname expans
Original Message
Subject: Re: shopt can't set extglob in a sub-shell?
Date: Mon, 27 Feb 2012 04:50:15 +0100
From: Davide Baldini <*@gmail.com>
Organization: Aioe.org NNTP Server
Newsgroups: gnu.bash.bug
[...]
On 02/26/12 12:41, John Kearney wrote:
> I updated
of the manual in my previous
"lost" message, here pasted:
---------
FROM Davide Baldini
On 02/27/12 04:11, Dan Douglas wrote:
> "If word is unquoted, all lines of the here-document are subjected to
> parameter expansion, command substitution, and arithmetic expansion."
&g
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
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
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
