[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Unexpected history expansion

From: John Kodis
Subject: Unexpected history expansion
Date: Sun, 05 Jan 2003 15:57:10 -0500

Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H  -I.  -I. -I./include -I./lib 
-D_GNU_SOURCE  -O2 -march=i386 -mcpu=i686
uname output: Linux daddy.kodis.org 2.4.18-19.8.0 #1 Thu Dec 12 05:39:29 EST 
2002 i686 i686 i386 GNU/Linux
Machine Type: i686-pc-linux-gnu

Bash Version: 2.05b
Patch Level: 0
Release Status: release


  The info page describing the event designators used by the bash
  history expansion mechanism say that an exclaimation point will:

      "Start a history substitution, except when followed by a space,
       tab, the end of the line, `=' or `('."

  However, bash tries to perform a history expansion even when the
  exclaimation point is followed by an opening parenthesis.


  Issuing pretty much any command containing an unescaped "!(" sequence,
  such as:

        $ ls !(*.c)
        bash: !: event not found


  Sorry, I'm not even sure whether this is a bash bug or a bash
  documentation bug, but the two are certainly at odds over this case.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]