summaryrefslogtreecommitdiff
path: root/runtime/doc/usr_27.txt
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2018-01-28 22:47:25 +0100
committerBram Moolenaar <Bram@vim.org>2018-01-28 22:47:25 +0100
commit40962ec9c0e7b8699e101182b06ddd39dc0e1212 (patch)
tree8949df2955a3d9cc6c0e4a6e89aa123a31c0abbd /runtime/doc/usr_27.txt
parent84b242c369a22b581c43de9de0152f0baedd71ab (diff)
downloadvim-git-40962ec9c0e7b8699e101182b06ddd39dc0e1212.tar.gz
Update runtime files.
Diffstat (limited to 'runtime/doc/usr_27.txt')
-rw-r--r--runtime/doc/usr_27.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/runtime/doc/usr_27.txt b/runtime/doc/usr_27.txt
index 44aa4063d..653ee4343 100644
--- a/runtime/doc/usr_27.txt
+++ b/runtime/doc/usr_27.txt
@@ -1,4 +1,4 @@
-*usr_27.txt* For Vim version 8.0. Last change: 2010 Mar 28
+*usr_27.txt* For Vim version 8.0. Last change: 2018 Jan 26
VIM USER MANUAL - by Bram Moolenaar
@@ -225,9 +225,9 @@ specify a line offset, this can cause trouble. For example: >
/const/-2
This finds the next word "const" and then moves two lines up. If you
-use "n" to search again, Vim could start at the current position and find the same
-"const" match. Then using the offset again, you would be back where you started.
-You would be stuck!
+use "n" to search again, Vim could start at the current position and find the
+same "const" match. Then using the offset again, you would be back where you
+started. You would be stuck!
It could be worse: Suppose there is another match with "const" in the next
line. Then repeating the forward search would find this match and move two
lines up. Thus you would actually move the cursor back!