| /vim-8.2.3635/src/testdir/ |
| H A D | test_system.vim | 12 call assert_equal(["as\<NL>df"], systemlist('cat', ["as\<NL>df"])) 18 call assert_equal(["as\r", "df\r"], systemlist('more.com', ["as\<NL>df"])) 22 call setline(1, ['asdf', "pw\<NL>er", 'xxxx']) 43 call assert_equal(['asdf', "pw\<NL>er", 'xxxx'], out)
|
| H A D | test_global.vim | 78 exe "g/foo/s/f/h/\<NL>s/o$/w/" 80 call setline(1, ["foo\<NL>bar"]) 81 exe "g/foo/s/foo\\\<NL>bar/xyz/"
|
| H A D | test27.in | 14 :" Need to add a NUL byte after the NL byte 24 :" Need to add three NUL bytes after the NL byte
|
| H A D | test_ga.vim | 36 " When using Mac fileformat, CR instead of NL is used for line termination
|
| H A D | test_messages.vim | 187 " Down a line with j, <CR>, <NL> or <Down>. 191 call term_sendkeys(buf, "\<NL>")
|
| /vim-8.2.3635/runtime/doc/ |
| H A D | os_dos.txt | 220 a single <NL> or a <CR><NL> pair for end-of-line (<EOL>). When writing a 221 file, Vim uses <CR><NL>. Thus, if you edit a file and write it, Vim replaces 222 <NL> with <CR><NL>. 224 If the 'fileformat' option is set to "unix", Vim uses a single <NL> for <EOL> 227 You can use Vim to replace <NL> with <CR><NL> by reading in any mode and 229 You can use Vim to replace <CR><NL> with <NL> by reading in Dos mode and 238 contain single <NL> characters which Vim would replace with <CR><NL>. You can
|
| H A D | channel.txt | 19 6. Using a RAW or NL channel |channel-raw| 53 NL every message ends in a NL (newline) character 145 excluding the NL. 401 first NL. This can also be just the NL for an empty response. 463 For a NL channel this returns one message. 528 in NL mode, the caller must do that. The NL in the response 580 "in_mode" "NL", "RAW", "JSON" or "JS" 644 For a NL channel this waits for a NL to arrive, except when 686 in NL mode, the caller must do that. The NL in the response 805 as NL bytes). [all …]
|
| H A D | usr_23.txt | 31 they could use <New Line> or <NL> only for end-of-line. The Apple people 33 <CR><NL> (we use <NL> for line feed in the help text). 58 unix <NL> 59 dos <CR><NL> 65 On Unix, <NL> is used to break a line. It's not unusual to have a <CR> 69 have a <NL> character halfway a line. 71 containing both <CR> and <NL> characters is a Mac or a Unix file. Therefore,
|
| H A D | editing.txt | 526 "dos" <CR><NL> or <NL> DOS format *DOS-format* 527 "unix" <NL> Unix format *Unix-format* 532 In DOS format (default for Win32), <CR><NL> and <NL> are both interpreted as 537 format <CR><NL> is used. Also see |DOS-format-write|. 540 replace all <CR><NL> pairs by <NL> (assuming 'fileformats' includes "dos"): > 555 <NL> pair (MS-Windows). Only when ALL lines end in <CR><NL>, 'fileformat' is 570 a file a <NL> was found, "[NL missing]" will be included in the file message. 579 single <NL> characters are unexpectedly replaced with <CR><NL>. 1424 file. Otherwise both <CR><NL> and <NL> are considered to end a line 1425 and when the file is written the <NL> will be replaced with <CR><NL>. [all …]
|
| H A D | insert.txt | 94 *i_CTRL-J* *i_<NL>* 95 <NL> or CTRL-J Begin new line. 294 (<NL>, value 10). There are five ways to enter the character value: 312 the buffer to a file, the <NL> character is translated into <Nul>. The <NL> 314 <NL> character in a file you will have to make a line break. 2062 "dos" <CR><NL> or <NL> DOS format 2063 "unix" <NL> Unix format 2072 <NUL>. See |CR-used-for-NL|. 2104 NL without a preceding CR was found. 2105 [NL found] reading with "mac" 'fileformat' and a [all …]
|
| H A D | vi_diff.txt | 464 characters (they are represented as <NL> internally). 551 Search patterns have more features. The <NL> character is seen as part of the 727 only for one line. "3iabc<NL>def<Esc>" would insert "abcabcabc<NL>def" in Vi 728 but "abc<NL>defabc<NL>defabc<NL>def" in Vim. 751 The 'fileformat' option can be set to select the <EOL>: "dos" <CR><NL>, "unix" 752 <NL> or "mac" <CR>. 796 than <CR>, <NL> and <Space> are interpreted as the (start of) a command. 910 |<NL>| same as "j" 1048 <NL> same as <CR>
|
| H A D | pattern.txt | 1146 NL, vertical tab, form feed 1273 Technical detail: *NL-used-for-Nul* 1274 <Nul> characters in the file are stored as <NL> in memory. In the display 1278 character is replaced with a <NL> in the search pattern. What is unusual is 1279 that typing CTRL-V CTRL-J also inserts a <NL>, thus also searches for a <Nul> 1282 *CR-used-for-NL* 1283 When 'fileformat' is "mac", <NL> characters in the file are stored as <CR> 1285 works similar to the usage of <NL> for a <Nul>. 1287 When working with expression evaluation, a <NL> character in the pattern 1288 matches a <NL> in the string. The use of "\n" (backslash n) to match a <NL>
|
| H A D | cmdline.txt | 147 the command line are inserted literally (<Esc>, <CR>, <NL>, 243 CTRL-M or CTRL-J *c_CTRL-M* *c_CTRL-J* *c_<NL>* *c_<CR>* *c_CR* 244 <CR> or <NL> start entered command 652 You can also use <NL> to separate commands in the same way as with '|'. To 653 insert a <NL> use CTRL-V CTRL-J. "^@" will be shown. Using '|' is the 654 preferred method. But for external commands a <NL> must be used, because a 655 '|' is included in the external command. To avoid the special meaning of <NL> 657 :r !date<NL>-join
|
| /vim-8.2.3635/runtime/spell/nl/ |
| H A D | nl_NL.diff | 8 # combined layout for BE and NL keyboards NL en BE 32 # combined layout for BE and NL keyboards NL en BE
|
| /vim-8.2.3635/src/ |
| H A D | ascii.h | 28 #define NL '\012' macro 107 #define NL '\x15' macro
|
| H A D | fileio.c | 1142 *ptr = NL; // split line by inserting a NL in readfile() 1236 if (p[ni] == NL) in readfile() 1250 if (p[ni] == NL) in readfile() 1255 ptr[tlen++] = NL; in readfile() 2090 if (*p == NL) in readfile() 2115 if (*p == NL) in readfile() 2154 if ((c = *ptr) != NUL && c != CAR && c != NL) in readfile() 2157 *ptr = NL; // NULs are replaced by newlines! in readfile() 2158 else if (c == NL) in readfile() 2194 if ((c = *ptr) != NUL && c != NL) // catch most common case in readfile() [all …]
|
| H A D | misc1.c | 975 else if (c == CAR || c == NL ) in get_number() 2418 if (putc(NL, fd) == EOF) in get_cmd_output_as_rettv() 2479 while (i < len && res[i] != NL) in get_cmd_output_as_rettv() 2488 *p = *start == NUL ? NL : *start; in get_cmd_output_as_rettv() 2518 if (s[0] == CAR && s[1] == NL) in get_cmd_output_as_rettv()
|
| H A D | bufwrite.c | 238 if (c == NL) in buf_write_bytes() 2030 if (c == NL) in buf_write() 2033 *s = NL; // Mac: replace CRs with NLs in buf_write() 2069 *s++ = NL; in buf_write() 2086 *s++ = NL; in buf_write()
|
| H A D | message.c | 2726 if (*s == NL) in msg_puts_printf() 2736 buf[n++] = NL; in msg_puts_printf() 2752 if (*s == CAR || *s == NL) in msg_puts_printf() 2760 if (*s == CAR || *s == NL) in msg_puts_printf() 2879 case NL: in do_more_prompt() 3805 case NL: in do_dialog()
|
| H A D | vim.rc | 10 // Must be in DOS format <CR><NL>!
|
| H A D | profiler.c | 874 if (IObuff[IOSIZE - 2] != NUL && IObuff[IOSIZE - 2] != NL) in script_dump_profile() 888 IObuff[n] = NL; in script_dump_profile()
|
| H A D | config.mk.in | 114 NL = @line_break@
|
| H A D | beval.c | 296 if (len > 0 && result[len - 1] == NL) in general_beval_cb()
|
| H A D | misc2.c | 897 {NL, (char_u *)"NL"}, 898 {NL, (char_u *)"NewLine"}, // Alternative name 899 {NL, (char_u *)"LineFeed"}, // Alternative name 900 {NL, (char_u *)"LF"}, // Alternative name
|
| /vim-8.2.3635/READMEdir/ |
| H A D | README_src.txt | 4 It is packed for Unix systems (NL line separator).
|