a2f844cfb4
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 |
||
|---|---|---|
| .. | ||
| pages | ||
| autoedit.asciidoc | ||
| coding-style.asciidoc | ||
| design.asciidoc | ||
| interfacing.asciidoc | ||
| json_ui.asciidoc | ||
| kak.1.asciidoc | ||
| kakoune_logo.svg | ||
| keymap | ||
| screenshot-i3.gif | ||
| screenshot-tmux.gif | ||
| writing_scripts.asciidoc | ||
