Filename expansion cannot cope with ^A (literal control A)

[Nicholas Clark]

Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: freebsd3.0
Compiler: cc
Compilation CFLAGS:  -DPROGRAM='bash' -DHOSTTYPE='i386' -DOSTYPE='freebsd3.0' 
-DMACHTYPE='i386-pc-freebsd3.0' -DSHELL  -DHAVE_CONFIG_H   -I. -I. -I./lib -O 
-pipe
uname output: FreeBSD plum.flirble.org 4.4-PRERELEASE FreeBSD 4.4-PRERELEASE 
#0: Fri Aug 10 07:10:14 BST 2001     
root@pear.flirble.org:/usr/src/sys/compile/PLUM  i386
Machine Type: i386-pc-freebsd3.0

Bash Version: 2.02
Patch Level: 1
Release Status: release

Description:
        Filename expansion cannot cope with literal control A in patterns.
        Patterns containing control A characters fail to match. If this is a
        known limitation is it not documented in the "Filename expansion"
        page.

Repeat-By:
        
        bash input such as ^A is the xterm representaiton of control-Q
        control-A (etc). ls is diplaying the non-printing characters as ?

        $ touch ^A^A
        $ ls -l ^A?
        ls: ?: No such file or directory
        $ touch ^B^B
        $ ls -l ^B?
        -rw-r--r--  1 nick  nick  0 Jun 26 09:54 ??

        $ touch Foo^A
        $ ls -l Fo?^A
        ls: Fo?: No such file or directory
        $ touch Foo^B
        $ ls -l Fo?^B
        -rw-r--r--  1 nick  nick  0 Jun 26 09:56 Foo?

        Notice how control-B works. Control-A does not.
        It is not documented as being a limitation.

        (I didn't make a file containing a control-A in its name
         deliberately. But I'm having trouble deleting it.
         I had to use emacs. I prefer bash and rm for that job)