Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update usr_27 from Vim 8.0 to 8.1 #229

Merged
merged 1 commit into from
Jun 8, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/usr_27.jax
Original file line number Diff line number Diff line change
@@ -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

Expand Down
8 changes: 4 additions & 4 deletions en/usr_27.txt
Original file line number Diff line number Diff line change
@@ -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

Expand Down Expand Up @@ -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!
Expand Down