[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: case modification operators misbehaviour?
From: |
Chet Ramey |
Subject: |
Re: case modification operators misbehaviour? |
Date: |
Wed, 14 Jan 2009 22:23:50 -0500 |
User-agent: |
Thunderbird 2.0.0.19 (Macintosh/20081209) |
Jan Schampera wrote:
> (I used the bashbug command to provide config information)
>
> 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='bash'
> -DSHELL -DHAVE_CONFIG_H -I. -I../bash -I../bash/include -I../bash/lib
> -g -O2 -Wall
> uname output: Linux mainserver 2.6.26-1-486 #1 Mon Dec 15 17:32:01 UTC
> 2008 i686 GNU/Linux
> Machine Type: i486-pc-linux-gnu
>
> Bash Version: 3.2
> Patch Level: 39
> Release Status: release
>
> Description:
>
> The case modification operators (for parameter expansion) seem to be
> puzzled.
>
> Two things I don't understand:
> - it seems to work word-wise (might be due to my misinterpretion of the
> default pattern)
It does work word-by-word, like the emacs-mode editing commands. I
would like feedback on whether or not that works better than the
alternative.
> - the case shown below (looks like a bug)
Yes, it's a bug. God knows what I was thinking.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
- Re: case modification operators misbehaviour?,
Chet Ramey <=