following is from :help NL-used-for-Nul
Technical detail:
<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}
my problem is:
as mentioned above, <NUL> is stored as <NL> in memory, but isn't <NL> the
character to split line? unix platform is assumed. Wouldn't this cause a
newline displayed on the screen if there is <null> character in the file?
another problem is that what is the difference between file and buffer? Why vim
is doing this?
Thanks everyone!
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.