| /freebsd/contrib/nvi/vi/ |
| H A D | v_right.c | 53 * Historically, "[cdsy]l" worked at the end of a line. Also, in v_right()
92 * Historically, if the $ is a motion, and deleting from in v_dollar()
109 * Historically, it was illegal to use $ as a motion command on in v_dollar()
110 * an empty line. Unfortunately, even though C was historically in v_dollar()
|
| H A D | v_paragraph.c | 143 * historically, a motion component was to the end of in v_paragraphf()
165 * sink. The } command historically moved to the end of the last in v_paragraphf()
167 * last line. It also historically worked on empty files, so we in v_paragraphf()
221 * The { command historically moved to the beginning of the first in v_paragraphb()
226 * paragraph movements did NOT historically pay attention to non-blank in v_paragraphb()
|
| H A D | v_mark.c | 46 * Although not commonly known, the "'`" and "'`" forms are historically
112 * Historically, BQMARKS for character positions that no longer in mark()
174 * historically behaved as follows: in mark()
|
| H A D | v_search.c | 148 * Historically, vi / and ? commands were full-blown ex addresses, in v_exaddr()
161 * Historically, if any part of the search command failed, the cursor in v_exaddr()
167 * Historically, the command "/STRING/; " failed, apparently it in v_exaddr()
211 * Historically, if it wasn't a motion command, a delta in the search in v_exaddr()
437 * Historically, commands didn't affect the line searched to/from if the
|
| H A D | vi.c | 142 * Vi historically flushed mapped characters on error, but in vi()
271 * Historically, commands which used mapped keys did not in vi()
545 * Historically, D accepted and then ignored a count. Match it. in v_cmd()
639 * Historically, half entered [[, ]] or Z commands weren't in v_cmd()
1043 * Historically, tag commands skipped over any leading whitespace in v_curword()
1071 * Historically, vi accepted any non-blank as initial character in v_curword()
1182 * Historically, ^V was ignored in the command stream, in v_key()
1198 * Historically, vi beeped on command level interrupts. in v_key()
1200 * Historically, vi exited to ex mode if no file was in v_key()
|
| H A D | v_z.c | 56 * A window size of 0 was historically allowed, and simply ignored. in v_z()
58 * O_WINDOW option, but that's not how it worked historically. in v_z()
|
| H A D | v_scroll.c | 45 * Another issue is that page and half-page scrolling commands historically
74 * Historically, 1G was legal in an empty file. in v_lgoto()
330 * which was historically wrong. The correct one is: in v_pagedown()
376 * which was historically wrong. The correct one is: in v_pageup()
|
| /freebsd/contrib/nvi/ex/ |
| H A D | ex_visual.c | 88 * Historically, if no line address was specified, the [p#l] flags in ex_visual()
110 * Historically, undoing a visual session was a single undo command, in ex_visual()
141 * Historically, if the user exited the vi screen(s) using an in ex_visual()
|
| H A D | ex_bang.c | 73 * If the command was modified by the expansion, it was historically in ex_bang()
120 * Historically, vi lines were replaced by both the stdout and stderr in ex_bang()
128 /* Autoprint is set historically, even if the command fails. */ in ex_bang()
|
| H A D | ex_filter.c | 73 * Historically, in the FILTER_READ case, the utility reads from in ex_filter()
115 * Historically, ex only directed stdout into the input pipe, in ex_filter()
165 * Historically, this behaves differently from ":r file" command, in ex_filter()
294 * Historically, the characters were passed unmodified to the terminal.
|
| H A D | ex_read.c | 137 * Historically, filter reads as the first ex command didn't in ex_read()
160 * Historically, the read command doesn't switch to in ex_read()
209 * Historically, the read and write commands renamed in ex_read()
244 * Historically, vi did not permit reads from non-regular files, nor in ex_read()
|
| H A D | ex.c | 79 * Initialize the text flags. The beautify edit option historically in ex()
269 * Permit extra colons at the start of the line. Historically, in ex_cmd()
271 * The stripping is done here because, historically, any command in ex_cmd()
283 * Historically, there was no escape or delimiter for a comment, e.g. in ex_cmd()
309 * Historically, in ex mode, lines containing only <blank> characters in ex_cmd()
352 * worked, historically). in ex_cmd()
371 * Historically, lines with multiple adjacent (or <blank> separated) in ex_cmd()
564 * Historically, the number option applied to both ex and vi. One in ex_cmd()
603 * Historically, '|' characters in the first argument of the ex, edit, in ex_cmd()
768 * Historically, vi permitted ^V's to escape <newline>'s in the .exrc in ex_cmd()
[all …]
|
| H A D | ex_at.c | 46 * Historically, [@*]<carriage-return> and [@*][@*] executed the most in ex_at()
68 * Historically the @ command took a range of lines, and the @ buffer in ex_at()
|
| H A D | ex_z.c | 76 * Historically, the "middleness" of the line overrode the in ex_z()
88 * Historically, z. set the absolute cursor mark. in ex_z()
|
| H A D | ex_txt.c | 37 * being entered. Since "\<cr>" was illegal historically (except for the one
150 * Historically, <carriage-return>'s in the command in ex_txt()
238 * Historically, the ^D command took (but then ignored) in ex_txt()
|
| H A D | ex_yank.c | 35 * Historically, yanking lines in ex didn't count toward the in ex_yank()
|
| /freebsd/usr.bin/tr/ |
| H A D | tr.1 | 338 System V has historically implemented character ranges using the syntax
381 utility has historically not permitted the manipulation of NUL bytes in
387 utility has historically been extremely forgiving of syntax errors,
|
| /freebsd/share/man/man9/ |
| H A D | hz.9 | 123 Historically, both the
141 Historically,
|
| /freebsd/share/doc/usd/13.viref/ |
| H A D | vi.cmd.roff | 37 Historically, implementations of
1027 Historically, any
1057 Historically, any
1919 Historically, any
1943 Historically, any
2452 Historically,
2474 Historically, any
2847 Historically, the
2935 Historically,
2960 Historically,
[all …]
|
| H A D | set.opt.roff | 21 Historically, only the full name and the official abbreviations
636 has historically scanned the first and last five lines of each file as
897 Historically, the
1062 historically read startup files that were owned by someone other than
1093 This option has historically made editor messages less verbose.
1128 historically bells the terminal for many obvious mistakes, e.g. trying
|
| /freebsd/sbin/init/ |
| H A D | NOTES | 33 'Historically, the implementation-dependent process that
71 of POSIX.1.' It goes on to say that historically the first open()
|
| /freebsd/sys/contrib/device-tree/Bindings/timer/ |
| H A D | snps,arc-timer.txt | 4 - Two identical copies TIMER0 and TIMER1 exist in ARC cores and historically
|
| /freebsd/share/mk/ |
| H A D | src.tools.mk | 3 # historically, however that name seemed to be ambiguous, as those tools
|
| /freebsd/contrib/file/ |
| H A D | RELEASE-PROCEDURE | 28 ChangeLog changes. Historically we don't mention magic changes in the
|
| /freebsd/contrib/nvi/common/ |
| H A D | mark.c | 126 * The absolute mark is initialized to lno 1/cno 0, and historically in mark_get()
236 * work, i.e. historically you could mark the "line" in an empty in mark_insdel()
|