From a2f844cfb4c624c4c49aa021f859ab3c6f4d48f3 Mon Sep 17 00:00:00 2001 From: Eric James Michael Ritz Date: Sun, 23 Sep 2018 12:43:22 -0400 Subject: [PATCH] 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 --- doc/pages/keys.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/pages/keys.asciidoc b/doc/pages/keys.asciidoc index eec07587..64942837 100644 --- a/doc/pages/keys.asciidoc +++ b/doc/pages/keys.asciidoc @@ -136,8 +136,8 @@ the Shift modifier and moving will extend each selection instead. repeat last object or *f*/*t* selection command *m*:: - select to matching character, see the `matching_pairs` option - in <> + select to the next sequence enclosed by matching character, see the + `matching_pairs` option in <> *x*:: select line on which the end of each selection lies (or next line when end lies