From: Kim F. Storm Date: Thu, 27 Jul 2006 23:20:52 +0000 (+0000) Subject: (Reading One Event): Fix last change. X-Git-Tag: emacs-pretest-22.0.90~1222 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=ae4bce6790e4b718b87bf8d77e66afcd1d53b037;p=emacs.git (Reading One Event): Fix last change. --- diff --git a/lispref/commands.texi b/lispref/commands.texi index 3c987632a33..10cd97400f8 100644 --- a/lispref/commands.texi +++ b/lispref/commands.texi @@ -2220,13 +2220,13 @@ If @code{cursor-in-echo-area} is non-@code{nil}, then @code{read-event} moves the cursor temporarily to the echo area, to the end of any message displayed there. Otherwise @code{read-event} does not move the cursor. -If @code{seconds} is non-@code{nil}, it should be a number specifying +If @var{seconds} is non-@code{nil}, it should be a number specifying the maximum time to wait for input, in seconds. If no input arrives within that time, @code{read-event} stops waiting and returns -@code{nil}. A floating-point value for @code{seconds} means to wait +@code{nil}. A floating-point value for @var{seconds} means to wait for a fractional number of seconds. Some systems support only a whole -number of seconds; on these systems, @code{seconds} is rounded down. -If @code{seconds} is @code{nil}, @code{read-event} waits as long as +number of seconds; on these systems, @var{seconds} is rounded down. +If @var{seconds} is @code{nil}, @code{read-event} waits as long as necessary for input to arrive. If @code{read-event} gets an event that is defined as a help character,