Mercurial > vim
diff runtime/doc/map.txt @ 14864:40ef13331e02
Update runtime files.
commit https://github.com/vim/vim/commit/95bafa296ae97bf420d5c74dd6db517b404c5df7
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Oct 2 13:26:25 2018 +0200
Update runtime files.
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Tue, 02 Oct 2018 13:30:07 +0200 |
| parents | 2f7e67dd088c |
| children | b101b193d5ff |
line wrap: on
line diff
--- a/runtime/doc/map.txt +++ b/runtime/doc/map.txt @@ -371,8 +371,9 @@ job running in the terminal. See |termi *omap-info* Operator-pending mappings can be used to define a movement command that can be -used with any operator. Simple example: ":omap { w" makes "y{" work like "yw" -and "d{" like "dw". +used with any operator. Simple example: > + :omap { w +makes "y{" work like "yw" and "d{" like "dw". To ignore the starting cursor position and select different text, you can have the omap start Visual mode to select the text to be operated upon. Example @@ -383,9 +384,11 @@ Normal mode commands find the first '(' before it. That usually is the function name. To enter a mapping for Normal and Visual mode, but not Operator-pending mode, -first define it for all three modes, then unmap it for Operator-pending mode: +first define it for all three modes, then unmap it for +Operator-pending mode: > :map xx something-difficult :ounmap xx + Likewise for a mapping for Visual and Operator-pending mode or Normal and Operator-pending mode.