From 77111ca68068796a49586328d8e47a87f292163a Mon Sep 17 00:00:00 2001 From: Chong Yidong Date: Tue, 25 Nov 2008 03:51:47 +0000 Subject: [PATCH] (Key Sequence Input): Fix typos. --- doc/lispref/commands.texi | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi index 2fa2268a095..4c5636afe6c 100644 --- a/doc/lispref/commands.texi +++ b/doc/lispref/commands.texi @@ -2249,11 +2249,11 @@ that @code{lookup-key} does not perform case conversion in this way. @vindex this-command-keys-shift-translated When reading input results in such a @dfn{shift-translation}, Emacs sets the variable @code{this-command-keys-shift-translated} to a -non-nil value. Lisp programs can examine this variable if they need -to modify their behavior when invoked by shift-translated keys. For -example, the function @code{handle-shift-selection} examines the value -of this variable to determine how to activate or deactivate the region -(@pxref{The Mark, handle-shift-selection}). +non-@code{nil} value. Lisp programs can examine this variable if they +need to modify their behavior when invoked by shift-translated keys. +For example, the function @code{handle-shift-selection} examines the +value of this variable to determine how to activate or deactivate the +region (@pxref{The Mark, handle-shift-selection}). The function @code{read-key-sequence} also transforms some mouse events. It converts unbound drag events into click events, and discards unbound -- 2.39.2