搜索部分和替换部分的语法任意不同。一些相同的代码被重复用于表示不同的事物。是的,这很混乱。
| How to type | In search, means: | In replacement, means:
----------------------------------------------------------------------------
\n | \n | End-of-line | <Nul> 0x0
^@ | CTRL-V CTRL-J | <Nul> 0x0 | <Nul> 0x0
\r | \r | Carriage return 0xD | "Break the line here"
^M | CTRL-Enter | Carriage return 0xD | "Break the line here"
\^M | \ CTRL-V CTRL-ENTER | \ + carriage return 0xD | Carriage return 0xD
搜索时,根据您的平台,0xD 可能会被隐藏,被视为“换行符”的一部分,所以是的...您始终可以恢复文件的完整性,并通过打开文件和做:
:e ++ff=unix
类似地,在替换时,“在此处换行”会根据您的平台执行不同的操作。它可能会插入0xA 或0xD 0xA 等。
如果这还不够糟糕:
Technical detail: *NL-used-for-Nul*
<Nul> characters in the file are stored as <NL> in memory. In the display
they are shown as "^@". The translation is done when reading and writing
files. To match a <Nul> with a search pattern you can just enter CTRL-@ or
"CTRL-V 000". This is probably just what you expect. Internally the
character is replaced with a <NL> in the search pattern. What is unusual is
that typing CTRL-V CTRL-J also inserts a <NL>, thus also searches for a <Nul>
in the file. {Vi cannot handle <Nul> characters in the file at all}
*CR-used-for-NL*
When 'fileformat' is "mac", <NL> characters in the file are stored as <CR>
characters internally. In the text they are shown as "^J". Otherwise this
works similar to the usage of <NL> for a <Nul>.
When working with expression evaluation, a <NL> character in the pattern
matches a <NL> in the string. The use of "\n" (backslash n) to match a <NL>
doesn't work there, it only works to match text in the buffer.
除非处理文字 0x0 或 0xD 字符,否则始终坚持使用 \n 进行搜索和使用 \r 进行替换是一个很好的经验法则,您可能已经知道了。
另见:
:h /\n
:h /\r
:h s/\n
:h s/\r
:h s/\<CR>