summary refs log tree commit diff stats
path: root/doc/ranger.pod
diff options
context:
space:
mode:
authortoonn <toonn@toonn.io>2019-09-02 14:18:52 +0200
committertoonn <toonn@toonn.io>2019-09-18 17:43:59 +0200
commit4b917d2752f7b8af98765e23101b4caeaaa8b8c9 (patch)
tree6700f878c4eaeeadf542430d1de6c5873313aef4 /doc/ranger.pod
parent9befac323ac6fc0c1d31aa7ce0dbe3bc9907377c (diff)
downloadranger-4b917d2752f7b8af98765e23101b4caeaaa8b8c9.tar.gz
Remove redundant copymap sections
The extra entries pointing from `copycmap` and co. to `copymap` only
contributed noise and confusion making their explanation harder to find.
This has summarily been dealt with using my exemplary SEO skills ; )

Fixes #1678
Diffstat (limited to 'doc/ranger.pod')
-rw-r--r--doc/ranger.pod16
1 files changed, 2 insertions, 14 deletions
diff --git a/doc/ranger.pod b/doc/ranger.pod
index 34a012ea..f6dd6592 100644
--- a/doc/ranger.pod
+++ b/doc/ranger.pod
@@ -1317,10 +1317,6 @@ Binds keys for the console. Works like the C<map> command.
 Opens the console with the command already typed in.  The cursor is placed at
 I<N>.
 
-=item copycmap I<key> I<newkey> [I<newkey2> ...]
-
-See C<copymap>
-
 =item copymap I<key> I<newkey> [I<newkey2> ...]
 
 Copies the keybinding I<key> to I<newkey> in the "browser" context.  This is a
@@ -1328,16 +1324,8 @@ deep copy, so if you change the new binding (or parts of it) later, the old one
 is not modified. For example, I<copymap j down> will make the key sequence
 "down" move the cursor down one item.
 
-To copy key bindings of the console, taskview, or pager use "copycmap",
-"copytmap" or "copypmap".
-
-=item copypmap I<key> I<newkey> [I<newkey2> ...]
-
-See C<copymap>
-
-=item copytmap I<key> I<newkey> [I<newkey2> ...]
-
-See C<copymap>
+To copy key bindings of the console, taskview or pager use "copycmap",
+"copytmap" or "copypmap" respectively.
 
 =item cunmap [I<keys...>]