[Top][All Lists]

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

Inconsistent handling of quotes in backticks

From: bronson
Subject: Inconsistent handling of quotes in backticks
Date: Wed, 21 Jul 2004 14:53:30 -0700 (PDT)

Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H  -I.  -I../bash -I../bash/include 
-I../bash/lib  -g -O2
uname output: Linux lea 2.6.5 #1 Tue Apr 6 12:07:18 PDT 2004 i686 GNU/Linux
Machine Type: i386-pc-linux-gnu

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


Bash treats quotes around the command name differently within backticks
than it does everywhere else.  This makes it quite difficult to use
bhe backticks to run an executable that has spaces in its name.


This shows that quotes around the command is perfectly fine:

        $ "echo" "hi"
        $ `"echo" "echo hi"`

However, if you put quotes around the command in a backtick substitution,
the command fails:

        $ `echo "\"echo\" hi"`
        bash: "echo": command not found

reply via email to

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