diff options
Diffstat (limited to 'runtime/doc/editing.txt')
| -rw-r--r-- | runtime/doc/editing.txt | 22 |
1 files changed, 18 insertions, 4 deletions
diff --git a/runtime/doc/editing.txt b/runtime/doc/editing.txt index c745f902ec..e6b7342195 100644 --- a/runtime/doc/editing.txt +++ b/runtime/doc/editing.txt @@ -1,4 +1,4 @@ -*editing.txt* For Vim version 7.2. Last change: 2008 Aug 09 +*editing.txt* For Vim version 7.2. Last change: 2009 Jun 10 VIM REFERENCE MANUAL by Bram Moolenaar @@ -270,7 +270,7 @@ If you want to keep the changed buffer without saving it, switch on the Normal mode. Otherwise same as |:edit|. *:vie* *:view* -:vie[w] [++opt] [+cmd] file +:vie[w][!] [++opt] [+cmd] file When used in Ex mode: Leave |Ex mode|, go back to Normal mode. Otherwise same as |:edit|, but set 'readonly' option for this buffer. {not in Vi} @@ -462,7 +462,10 @@ converted and illegal bytes. It can be one of three things: ++bad=drop Remove the bad characters. The default is like "++bad=?": Replace each bad character with a question -mark. +mark. In some places an inverted question mark is used (0xBF). + +Note that not all commands use the ++bad argument, even though they do not +give an error when you add it. E.g. |:write|. Note that when reading, the 'fileformat' and 'fileencoding' options will be set to the used format. When writing this doesn't happen, thus a next write @@ -837,7 +840,7 @@ USING THE ARGUMENT LIST Example: > :args *.c :argdo set ff=unix | update -This sets the 'fileformat' option to "unix" and writes the file if is now +This sets the 'fileformat' option to "unix" and writes the file if it is now changed. This is done for all *.c files. Example: > @@ -1456,6 +1459,17 @@ If you don't get warned often enough you can use the following command. may be specified by name, number or with a pattern. + *E813* *E814* +Vim will reload the buffer if you chose to. If a window is visible that +contains this buffer, the reloading will happen in the context of this window. +Otherwise a special window is used, so that most autocommands will work. You +can't close this window. A few other restrictions apply. Best is to make +sure nothing happens outside of the current buffer. E.g., setting +window-local options may end up in the wrong window. Splitting the window, +doing something there and closing it should be OK (if there are no side +effects from other autocommands). Closing unrelated windows and buffers will +get you into trouble. + Before writing a file the timestamp is checked. If it has changed, Vim will ask if you really want to overwrite the file: |