我在 Ubuntu 16.04 上,给出了以下test.file
内容:
Hello \there
为什么会这样(从命令行):
sed 's#\\there#where#' test.file
可以工作,但是这个:
sed "s#\\there#where#" test.file
没有?这是配置问题吗?
前者成功替换了模式,而后者似乎找不到任何匹配项。
我需要在脚本中的替换文本中使用变量,所以我(猜想)需要在 sed 命令周围加上双引号。
答案1
在bash
和其他 shell 中,反斜杠字符在单引号或双引号内的处理方式不同。
当您键入时sed 's#\\there#where#' test.file
,sed
其运行字符串中看到的是s#\\there#where# test.file
,因为单引号会阻止所有特殊字符和转义序列解释:甚至\'
是不允许的。
当您键入时sed "s#\\there#where#" test.file
,sed
在其运行字符串中看到的是s#\there#where# test.file
,因为双引号允许一些转义序列,并且 shell 已将第一个反斜杠解释为转义第二个反斜杠。
进一步的复杂之处在于sed
还允许转义序列解释,类似于双引号中的转义序列解释,因此在第一种情况下(单引号),搜索字符串将变成\there
您想要的 ; 而在第二种情况下(双引号),搜索字符串的第一个字符变成Tab,后跟here
。
以下摘自bash
手册的内容定义了这些操作:-
There are three quoting mechanisms: the escape character, single quotes, and double quotes. A non-quoted backslash (\) is the escape character. It preserves the literal value of the next character that follows, with the exception of <newline>. If a \<newline> pair appears, and the backslash is not itself quoted, the \<newline> is treated as a line continuation (that is, it is removed from the input stream and effectively ignored). Enclosing characters in single quotes preserves the literal value of each character within the quotes. A sin‐ gle quote may not occur between single quotes, even when preceded by a backslash. Enclosing characters in double quotes preserves the literal value of all characters within the quotes, with the exception of $, `, \, and, when history expansion is enabled, !. The characters $ and ` retain their spe‐ cial meaning within double quotes. The backslash retains its special meaning only when followed by one of the following characters: $, `, ", \, or <newline>. A double quote may be quoted within double quotes by preced‐ ing it with a backslash. If enabled, history expansion will be performed unless an ! appearing in double quotes is escaped using a backslash. The backslash preceding the ! is not removed. The special parameters * and @ have special meaning when in double quotes (see PARAMETERS below). Words of the form $'string' are treated specially. The word expands to string, with backslash-escaped charac‐ ters replaced as specified by the ANSI C standard. Backslash escape sequences, if present, are decoded as follows: \a alert (bell) \b backspace \e \E an escape character \f form feed \n new line \r carriage return \t horizontal tab \v vertical tab \\ backslash \' single quote \" double quote \nnn the eight-bit character whose value is the octal value nnn (one to three digits) \xHH the eight-bit character whose value is the hexadecimal value HH (one or two hex digits) \uHHHH the Unicode (ISO/IEC 10646) character whose value is the hexadecimal value HHHH (one to four hex digits) \UHHHHHHHH the Unicode (ISO/IEC 10646) character whose value is the hexadecimal value HHHHHHHH (one to eight hex digits) \cx a control-x character The expanded result is single-quoted, as if the dollar sign had not been present. A double-quoted string preceded by a dollar sign ($"string") will cause the string to be translated according to the current locale. If the current locale is C or POSIX, the dollar sign is ignored. If the string is translated and replaced, the replacement is double-quoted.