Improve the documentation for the 'm' key
The GitHub issue referenced below describes the default behavior of the 'm' key in a way that was unknown to me. As the issue says, "'m' is a pretty misunderstood key", and goes on to describe how the documentation makes it sound as if the cursor must be on the matching character before 'm' will work. However, this is not true; pressing 'm' will jump forward to "select the next sequence enclosed in balanced chars". This patch updates the documentation so that it describes that behavior. GitHub-Issue: #2425 Special-thanks: Delapouite
This commit is contained in:
parent
1631a7d8d9
commit
a2f844cfb4
|
@ -136,8 +136,8 @@ the Shift modifier and moving will extend each selection instead.
|
||||||
repeat last object or *f*/*t* selection command
|
repeat last object or *f*/*t* selection command
|
||||||
|
|
||||||
*m*::
|
*m*::
|
||||||
select to matching character, see the `matching_pairs` option
|
select to the next sequence enclosed by matching character, see the
|
||||||
in <<options#,`:doc options`>>
|
`matching_pairs` option in <<options#,`:doc options`>>
|
||||||
|
|
||||||
*x*::
|
*x*::
|
||||||
select line on which the end of each selection lies (or next line when end lies
|
select line on which the end of each selection lies (or next line when end lies
|
||||||
|
|
Loading…
Reference in New Issue
Block a user