Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/s
On Wednesday 16 July 2008 04:47, Lawrence D'Oliveiro wrote:
> Description:
> In all contexts in which a character "X" has special meaning to bash, it
> should be possible to insert that character literally by writing "\X".
> This fails in one case: where "X" is "!", and the context is inside doubl
> Machine Type: x86_64-pc-linux-gnu
>
> Bash Version: 3.2
> Patch Level: 39
> Release Status: release
>
> Description:
> In all contexts in which a character "X" has special meaning to bash,
> it should
> be possible to insert that character literally by writing "\X". This
> fails i
On 2008-07-16, Chet Ramey wrote:
>> Machine Type: x86_64-pc-linux-gnu
>>
>> Bash Version: 3.2
>> Patch Level: 39
>> Release Status: release
>>
>> Description:
>> In all contexts in which a character "X" has special meaning to bash,
>> it should
>> be possible to insert that character l
Chris F.A. Johnson wrote:
With LC_COLLATE set to a locale with case-insensitive collation,
filename expansion does not use the locale. It does with LC_ALL.
In an empty directory:
$ touch a B c D e F
$ echo *
B D F a c e
$ LC_COLLATE=en_us
$ echo *
B D F a c e
$ LC_ALL=en_us
$ echo *
a B c D e F
*"You might be able to avoid the need for the getcwd call at startup by
exporting PWD*"
Sorry,would you give us more details about how to avoid the "error" message
Thanks very much
LynnOS
2008/7/13 Chet Ramey <[EMAIL PROTECTED]>:
> [EMAIL PROTECTED] wrote:
>
> LynnOS wrote:
>>
>>> [EMAIL PROT
