diff options
author | Bram Moolenaar <Bram@vim.org> | 2005-02-22 08:28:13 +0000 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2005-02-22 08:28:13 +0000 |
commit | 6bdcfc08cb9c192972336e28a2a842b7abbb2811 (patch) | |
tree | eb505f35bdcf67590ad3425db032513be720a437 | |
parent | 81bf70834198428f10681eea8630732fa7aeafdb (diff) |
updated for version 7.0051
-rw-r--r-- | runtime/doc/vi_diff.txt | 54 |
1 files changed, 44 insertions, 10 deletions
diff --git a/runtime/doc/vi_diff.txt b/runtime/doc/vi_diff.txt index 78993f0a33..de9c47798c 100644 --- a/runtime/doc/vi_diff.txt +++ b/runtime/doc/vi_diff.txt @@ -1,4 +1,4 @@ -*vi_diff.txt* For Vim version 7.0aa. Last change: 2005 Feb 10 +*vi_diff.txt* For Vim version 7.0aa. Last change: 2005 Feb 21 VIM REFERENCE MANUAL by Bram Moolenaar @@ -14,7 +14,7 @@ Vim is mostly POSIX 1003.2-1 compliant. The only command known to be missing is ":open". There are probably a lot of small differences (either because Vim is missing something or because Posix is beside the mark). -1. Missing commands |missing-commands| +1. Simulated command |simulated-command| 2. Missing options |missing-options| 3. Limits |limits| 4. The most interesting additions |vim-additions| @@ -23,11 +23,22 @@ is missing something or because Posix is beside the mark). 7. POSIX compliance |posix-compliance| ============================================================================== -1. Missing commands *missing-commands* +1. Simulated command *simulated-command* -This command is in Vi, but not in Vim: +This command is in Vi, but Vim only simuates it: -:o[pen] {Vi: start editing in open mode} *:o* *:op* *:open* + *:o* *:op* *:open* +:[range]o[pen] Works like |:visual|: end Ex mode. + {Vi: start editing in open mode} + +:[range]o[pen] /pattern/ As above, additionally move the cursor to the + column where "pattern" matches in the cursor + line. + +Vim does not support open mode, since it's not really useful. For those +situations where ":open" would start open mode Vim will leave Ex mode, which +allows executing the same commands, but updates the whole screen instead of +only one line. ============================================================================== 2. Missing options *missing-options* @@ -46,7 +57,6 @@ mesg boolean (default on) *'mesg'* novice boolean (default off) *'novice'* open boolean (default on) *'open'* optimize (op) boolean (default off) *'optimize'* *'op'* -prompt boolean (default on) *'prompt'* redraw boolean (default off) *'redraw'* slowopen (slow) boolean (default off) *'slowopen'* *'slow'* sourceany boolean (default off) *'sourceany'* @@ -886,16 +896,14 @@ Only Vim is able to accept options in between and after the file names. In 2005 the POSIX test suite was run to check the compatiblity of Vim. Most of the test was executed properly. There are the few things where Vim -is not POSIX compliant. +is not POSIX compliant, even when run in Vi compatibility mode. Set the $VIM_POSIX environment variable to have 'cpoptions' include the POSIX flags when Vim starts up. This makes Vim run as POSIX as it can. That's -different from being Vi compatible. +a bit different from being Vi compatible. This is where Vim does not behave as POSIX specifies and why: - The -w{number} and -w {number} command line arguments are not - supported by Vim. *posix-screen-size* The $COLUMNS and $LINES environment variables are ignored by Vim if the size can be obtained from the terminal in a more reliable way. @@ -909,5 +917,31 @@ This is where Vim does not behave as POSIX specifies and why: The "D", "o" and "O" commands accept a count. Also when repeated. Add the '#' flag to 'cpoptions' if you want to ignore the count. + The ":cd" command fails if the current buffer is modified when the '.' + flag is present in 'cpoptions'. + + There is no ATTENTION message, the "A" flag is added to 'shortmess'. + +These are remarks about running the POSIX test suite: +- vi test 33 sometimes fails for unknown reasons +- vi test 250 fails; behavior will be changed in a new revision + http://www.opengroup.org/austin/mailarchives/ag-review/msg01710.html +- vi test 310 fails; exit code non-zero when any error occurred? +- ex test 24 fails because test is wrong. Changed between SUSv2 and SUSv3. +- ex tests 47, 48, 49, 72, 73 fail because .exrc file isn't read in silent + mode and $EXINIT isn't used. +- ex tests 76, 78 fail because echo is used instead of printf. (fixed) + Also: problem with \s not changed to space. +- ex test 355 fails because 'window' isn't used for "30z". +- ex test 368 fails because shell command isn't echoed in silent mode. +- ex test 394 fails because "=" command output isn't visible in silent mode. +- ex test 411 fails because test file is wrong, contains stray ':'. +- ex test 475 and 476 fail because reprint output isn't visible in silent mode. +- ex test 480 and 481 fail because the tags file has spaces instead of a tab. +- ex test 502 fails because .exrc isn't read in silent mode. +- ex test 509 fails because .exrc isn't read in silent mode. and exit code is + 1 instead of 2. +- ex test 534 fails because .exrc isn't read in silent mode. + vim:tw=78:ts=8:ft=help:norl: |