From d8b2bd71eb6c0404a70e300775eb60bbf12b6234 Mon Sep 17 00:00:00 2001 From: mnishz Date: Fri, 8 Jun 2018 17:01:15 +0900 Subject: [PATCH] Update usr_27 from Vim 8.0 to 8.1 --- doc/usr_27.jax | 2 +- en/usr_27.txt | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/usr_27.jax b/doc/usr_27.jax index dce800e7e..b56cd6969 100644 --- a/doc/usr_27.jax +++ b/doc/usr_27.jax @@ -1,4 +1,4 @@ -*usr_27.txt* For Vim バージョン 8.0. Last change: 2010 Mar 28 +*usr_27.txt* For Vim バージョン 8.1. Last change: 2018 Jan 26 VIM USER MANUAL - by Bram Moolenaar diff --git a/en/usr_27.txt b/en/usr_27.txt index 44aa4063d..7098c070d 100644 --- a/en/usr_27.txt +++ b/en/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.1. 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!