I'm trying to replace each ,
in the current file by a new line:
:%s/,/\n/g
But it inserts what looks like a ^@
instead of an actual newline. The file is not in DOS mode or anything.
What should I do?
If you are curious, like me, check the question Why is \r a newline for Vim? as well.
Use
\r
instead of\n
.Substituting by
\n
inserts a null character into the text. To get a newline, use\r
. When searching for a newline, you’d still use\n
, however. This asymmetry is due to the fact that\n
and\r
do slightly different things:\n
matches an end of line (newline), whereas\r
matches a carriage return. On the other hand, in substitutions\n
inserts a null character whereas\r
inserts a newline (more precisely, it’s treated as the input <CR>). Here’s a small, non-interactive example to illustrate this, using the Vim command line feature (in other words, you can copy and paste the following into a terminal to run it).xxd
shows a hexdump of the resulting file.In other words,
\n
has inserted the byte 0x00 into the text;\r
has inserted the byte 0x0a.This is the best answer for the way I think but it would have been nicer in a table: https://stackoverflow.com/a/12389839/962394.
So, rewording:
You need to use
\r
to use a line feed (ascii0x0a
, the unix newline) in a regex replacement but that is peculiar to the replacement - you should normally continue to expect to use\n
for line feed and\r
for carriage return.This is because vim used
\n
in a replacement to mean the NIL character (ascii0x00
). You might have expected NIL to have been\0
instead, freeing\n
for its usual use for line feed, but\0
already has a meaning in regex replacements so it was shifted to\n
. Hence then going further to also shift the newline from\n
to\r
(which in a regex pattern is the carriage return character, ascii0x0d
).NB:
^M
(Ctrl-V Ctrl-M on linux) inserts a newline when used in a regex replacement rather than a carriage return as others have advised (I just tried it).Also note that vim will translate the line feed character when it saves to file based on its file format settings and that might confuse matters.
In the syntax
s/foo/bar
\r
and\n
have different meanings, depending on context.short:
For
foo
:\n = newline (LF on linux/mac, CRLF on windows)
\r = carriage return (CR)
For
bar
:\r = is newline
\n = null byte.
longer: (with ascii numbers)
NUL
= 0x00 = 0 = CTRL@LF
= 0x0A = 10 = CTRLJCR
= 0x0D = 13 = CTRLMHere is a list of the ASCII control characters, insert them in
vim
via CTRLvCTRL---key---.In
bash
or the other unix/linux shells just type CTRL---key---. Try CTRLM in bash, its the same as hitting ENTER, as the shell realizes what is meant, even though linux systems use Line Feeds for line delimiting.To insert literal's in bash, prepending them with CTRLv will also work.
Try in bash:
This uses ANSI escape sequences, insert the two
^[
's via CTRLvESC.You might also try CTRLvCTRLmENTER, which will give you this:
Remember the
\r
from above? :>This ASCII control characters list is different from a complete ASCII symbol table, in that the control characters, which are inserted into a console/pseudoterminal/vim via the CTRL key (haha), can be found there. Whereas in C and most other languages you usually use the octal codes to represent these 'characters'.
If you really want to know where all this comes from: http://www.linusakesson.net/programming/tty/.
This is the best link you will come across about this topic, but beware: There be dragons.
TL;DR
Usually
foo
=\n
, andbar
=\r
.If you need to do for a whole file, it was also suggested to me that you could try from the command line
\r
can do the work here for you.Here's the trick:
First, set your vi(m) session to allow pattern matching with special characters (ie: newline). It's probably worth putting this line in your .vimrc or .exrc file.
Next, do:
To get the
^M
character, type Control-v and hit Enter. Under Windows, do Control-q, Enter. The only way I can remember these is by remembering how little sense they make: