bash 脚本使用双引号、单引号和空格执行命令

Question

I've looked at the similar posts about this problem, but cannot figure out how to get the executed code to be in the correct format, which needs to be foo --bar "a='b'" . My best attempt at this was

#!/bin/bash -x

bar='--bar ''"''a='"'"'b'"'"'"'
cmd=(foo $bar)
echo ${cmd[@]}
eval ${cmd[@]}

The output from this is correct for the echo , but incorrect for eval

+ bar='--bar "a='\''b'\''"'
+ cmd=(foo $bar)
+ echo foo --bar '"a='\''b'\''"'
foo --bar "a='b'"
+ eval foo --bar '"a='\''b'\''"'
++ foo --bar 'a='\''b'\'''

What is the correct way to execute the command with the option?

Answer 1

If you must store command fragments, use functions or arrays, not strings.

An example of best-practice code, in accordance with BashFAQ #50 :

#!/usr/bin/env bash
bar=( --bar a="b" )
cmd=(foo "${bar[@]}" )
printf '%q ' "${cmd[@]}" && echo  # print code equivalent to the command we're about to run
"${cmd[@]}"                       # actually run this code

---

Bonus: Your debug output doesn't prove what you think it does.

"a='b'" and 'a='\\''b'\\''' are two different ways to quote the exact same string .

To prove this:

printf '%s\n' "a='b'" | md5sum -
printf '%s\n' 'a='\''b'\''' | md5sum -

...emits as output:

7f183df5823cf51ec42a3d4d913595d7  -
7f183df5823cf51ec42a3d4d913595d7  -

...so there's nothing at all different between how the arguments to echo $foo and eval $foo are being parsed in your code.

Why is this true? Because syntactic quotes aren't part of the command that's actually run; they're removed by the shell after it uses them to determine how to interpret a command line character-by-character.

So, let's break down what set -x is showing you:

'a='\''b'\'''

...consists of the following literal strings concatenated together:

• a= (in a single-quoted context that is entered and ended by the single quotes surrounding)
• ' (in an unquoted context, escaped by the backslash that precedes it)
• b (in a single-quoted context that is entered and ended by the single quotes surrounding)
• ' (in an unquoted context)

...everything else is syntactic , meaningful to the shell but not ever passed to the program foo .

Answer 2

If you want exactly the same expansion to happen as in echo ${cmd[@]} , just run the command then:

${cmd[@]}

It will execute:

+ foo --bar '"a='\''b'\''"'

Note that because it is unquoted, for example * will be expanded according to filename expansion .