From d43f4539cc450f6cd13a9c7318fe9bece41ae5da Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Thu, 13 Jan 2005 19:53:58 +0000 Subject: [PATCH] (Commands): Clarification. --- man/commands.texi | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/man/commands.texi b/man/commands.texi index 54ec50acfe8..cc8537c1271 100644 --- a/man/commands.texi +++ b/man/commands.texi @@ -222,13 +222,15 @@ this effect @emph{because} it is bound to that command. If you rebind forward by words instead. Rebinding keys is a common method of customization.@refill - In the rest of this manual, we usually ignore this subtlety to keep -things simple. To give the information needed for customization, we -state the name of the command which really does the work in parentheses + In the rest of this manual, we usually ignore this distinction to +keep things simple. We will often speak of keys like @kbd{C-n} as +commands, even though strictly speaking a key is bound to some +command. To give the information needed for customization, we state +the name of the command which really does the work in parentheses after mentioning the key that runs it. For example, we will say that ``The command @kbd{C-n} (@code{next-line}) moves point vertically -down,'' meaning that @code{next-line} is a command that moves vertically -down, and @kbd{C-n} is a key that is normally bound to it. +down,'' meaning that @code{next-line} is a command that moves +vertically down, and @kbd{C-n} is a key that is normally bound to it. While we are on the subject of information for customization only, it's a good time to tell you about @dfn{variables}. Often the -- 2.39.2