[Emacs-diffs] Changes to emacs/lispref/commands.texi

[Miles Bader]

Index: emacs/lispref/commands.texi
diff -c emacs/lispref/commands.texi:1.37 emacs/lispref/commands.texi:1.38
*** emacs/lispref/commands.texi:1.37    Sat Dec  7 16:42:43 2002
--- emacs/lispref/commands.texi Tue Feb  4 09:47:52 2003
***************
*** 1,7 ****
  @c -*-texinfo-*-
  @c This is part of the GNU Emacs Lisp Reference Manual.
  @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999
! @c   Free Software Foundation, Inc. 
  @c See the file elisp.texi for copying conditions.
  @setfilename ../info/commands
  @node Command Loop, Keymaps, Minibuffers, Top
--- 1,7 ----
  @c -*-texinfo-*-
  @c This is part of the GNU Emacs Lisp Reference Manual.
  @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999
! @c   Free Software Foundation, Inc.
  @c See the file elisp.texi for copying conditions.
  @setfilename ../info/commands
  @node Command Loop, Keymaps, Minibuffers, Top
***************
*** 12,18 ****
    When you run Emacs, it enters the @dfn{editor command loop} almost
  immediately.  This loop reads key sequences, executes their definitions,
  and displays the results.  In this chapter, we describe how these things
! are done, and the subroutines that allow Lisp programs to do them.  
  
  @menu
  * Command Overview::    How the command loop reads commands.
--- 12,18 ----
    When you run Emacs, it enters the @dfn{editor command loop} almost
  immediately.  This loop reads key sequences, executes their definitions,
  and displays the results.  In this chapter, we describe how these things
! are done, and the subroutines that allow Lisp programs to do them.
  
  @menu
  * Command Overview::    How the command loop reads commands.
***************
*** 442,448 ****
  @comment  node-name,  next,  previous,  up
  @subsection Examples of Using @code{interactive}
  @cindex examples of using @code{interactive}
! @cindex @code{interactive}, examples of using 
  
    Here are some examples of @code{interactive}:
  
--- 442,448 ----
  @comment  node-name,  next,  previous,  up
  @subsection Examples of Using @code{interactive}
  @cindex examples of using @code{interactive}
! @cindex @code{interactive}, examples of using
  
    Here are some examples of @code{interactive}:
  
***************
*** 501,507 ****
  
  @defun commandp object
  Returns @code{t} if @var{object} is suitable for calling interactively;
! that is, if @var{object} is a command.  Otherwise, returns @code{nil}.  
  
  The interactively callable objects include strings and vectors (treated
  as keyboard macros), lambda expressions that contain a top-level call to
--- 501,507 ----
  
  @defun commandp object
  Returns @code{t} if @var{object} is suitable for calling interactively;
! that is, if @var{object} is a command.  Otherwise, returns @code{nil}.
  
  The interactively callable objects include strings and vectors (treated
  as keyboard macros), lambda expressions that contain a top-level call to
***************
*** 664,670 ****
  @section Information from the Command Loop
  
  The editor command loop sets several Lisp variables to keep status
! records for itself and for commands that are run.  
  
  @defvar last-command
  This variable records the name of the previous command executed by the
--- 664,670 ----
  @section Information from the Command Loop
  
  The editor command loop sets several Lisp variables to keep status
! records for itself and for commands that are run.
  
  @defvar last-command
  This variable records the name of the previous command executed by the
***************
*** 1272,1278 ****
  @key{meta} held down comes to the Lisp program as
  @code{M-double-mouse-2}.  If a double-click event has no binding, the
  binding of the corresponding ordinary click event is used to execute
! it.  Thus, you need not pay attention to the double click feature 
  unless you really want to.
  
  When the user performs a double click, Emacs generates first an ordinary
--- 1272,1278 ----
  @key{meta} held down comes to the Lisp program as
  @code{M-double-mouse-2}.  If a double-click event has no binding, the
  binding of the corresponding ordinary click event is used to execute
! it.  Thus, you need not pay attention to the double click feature
  unless you really want to.
  
  When the user performs a double click, Emacs generates first an ordinary
***************
*** 2131,2137 ****
  For example, the function that implements numeric prefix arguments reads
  any number of digits.  When it finds a non-digit event, it must unread
  the event so that it can be read normally by the command loop.
! Likewise, incremental search uses this feature to unread events with no 
  special meaning in a search, because these events should exit the search
  and then execute normally.
  
--- 2131,2137 ----
  For example, the function that implements numeric prefix arguments reads
  any number of digits.  When it finds a non-digit event, it must unread
  the event so that it can be read normally by the command loop.
! Likewise, incremental search uses this feature to unread events with no
  special meaning in a search, because these events should exit the search
  and then execute normally.
  
***************
*** 2200,2206 ****
  
  In the following example, the user may type a number of characters right
  after starting the evaluation of the form.  After the @code{sleep-for}
! finishes sleeping, @code{discard-input} discards any characters typed 
  during the sleep.
  
  @example
--- 2200,2206 ----
  
  In the following example, the user may type a number of characters right
  after starting the evaluation of the form.  After the @code{sleep-for}
! finishes sleeping, @code{discard-input} discards any characters typed
  during the sleep.
  
  @example
***************
*** 2251,2257 ****
  This function performs redisplay (provided there is no pending input
  from the user), then waits @var{seconds} seconds, or until input is
  available.  The value is @code{t} if @code{sit-for} waited the full
! time with no input arriving (see @code{input-pending-p} in @ref{Event 
  Input Misc}).  Otherwise, the value is @code{nil}.
  
  The argument @var{seconds} need not be an integer.  If it is a floating
--- 2251,2257 ----
  This function performs redisplay (provided there is no pending input
  from the user), then waits @var{seconds} seconds, or until input is
  available.  The value is @code{t} if @code{sit-for} waited the full
! time with no input arriving (see @code{input-pending-p} in @ref{Event
  Input Misc}).  Otherwise, the value is @code{nil}.
  
  The argument @var{seconds} need not be an integer.  If it is a floating
***************
*** 2334,2340 ****
    At the level of C code, quitting cannot happen just anywhere; only at the
  special places that check @code{quit-flag}.  The reason for this is
  that quitting at other places might leave an inconsistency in Emacs's
! internal state.  Because quitting is delayed until a safe place, quitting 
  cannot make Emacs crash.
  
    Certain functions such as @code{read-key-sequence} or
--- 2334,2340 ----
    At the level of C code, quitting cannot happen just anywhere; only at the
  special places that check @code{quit-flag}.  The reason for this is
  that quitting at other places might leave an inconsistency in Emacs's
! internal state.  Because quitting is delayed until a safe place, quitting
  cannot make Emacs crash.
  
    Certain functions such as @code{read-key-sequence} or
***************
*** 2343,2349 ****
  input.  In the case of @code{read-key-sequence}, this serves to bring
  about the special behavior of @kbd{C-g} in the command loop.  In the
  case of @code{read-quoted-char}, this is so that @kbd{C-q} can be used
! to quote a @kbd{C-g}.  
  
  @cindex prevent quitting
    You can prevent quitting for a portion of a Lisp function by binding
--- 2343,2349 ----
  input.  In the case of @code{read-key-sequence}, this serves to bring
  about the special behavior of @kbd{C-g} in the command loop.  In the
  case of @code{read-quoted-char}, this is so that @kbd{C-q} can be used
! to quote a @kbd{C-g}.
  
  @cindex prevent quitting
    You can prevent quitting for a portion of a Lisp function by binding
***************
*** 2399,2405 ****
  
    You can specify a character other than @kbd{C-g} to use for quitting.
  See the function @code{set-input-mode} in @ref{Terminal Input}.
!  
  @node Prefix Command Arguments
  @section Prefix Command Arguments
  @cindex prefix argument
--- 2399,2405 ----
  
    You can specify a character other than @kbd{C-g} to use for quitting.
  See the function @code{set-input-mode} in @ref{Terminal Input}.
! 
  @node Prefix Command Arguments
  @section Prefix Command Arguments
  @cindex prefix argument
***************
*** 2468,2478 ****
  
  M-3     M-x display-prefix  @print{} 3      ; @r{(Same as @code{C-u 3}.)}
  
! C-u -   M-x display-prefix  @print{} -      
  
  M--     M-x display-prefix  @print{} -      ; @r{(Same as @code{C-u -}.)}
  
! C-u - 7 M-x display-prefix  @print{} -7     
  
  M-- 7   M-x display-prefix  @print{} -7     ; @r{(Same as @code{C-u -7}.)}
  @end example
--- 2468,2478 ----
  
  M-3     M-x display-prefix  @print{} 3      ; @r{(Same as @code{C-u 3}.)}
  
! C-u -   M-x display-prefix  @print{} -
  
  M--     M-x display-prefix  @print{} -      ; @r{(Same as @code{C-u -}.)}
  
! C-u - 7 M-x display-prefix  @print{} -7
  
  M-- 7   M-x display-prefix  @print{} -7     ; @r{(Same as @code{C-u -7}.)}
  @end example
***************
*** 2633,2644 ****
  @deffn Command exit-recursive-edit
  This function exits from the innermost recursive edit (including
  minibuffer input).  Its definition is effectively @code{(throw 'exit
! nil)}.  
  @end deffn
  
  @deffn Command abort-recursive-edit
  This function aborts the command that requested the innermost recursive
! edit (including minibuffer input), by signaling @code{quit} 
  after exiting the recursive edit.  Its definition is effectively
  @code{(throw 'exit t)}.  @xref{Quitting}.
  @end deffn
--- 2633,2644 ----
  @deffn Command exit-recursive-edit
  This function exits from the innermost recursive edit (including
  minibuffer input).  Its definition is effectively @code{(throw 'exit
! nil)}.
  @end deffn
  
  @deffn Command abort-recursive-edit
  This function aborts the command that requested the innermost recursive
! edit (including minibuffer input), by signaling @code{quit}
  after exiting the recursive edit.  Its definition is effectively
  @code{(throw 'exit t)}.  @xref{Quitting}.
  @end deffn
***************
*** 2780,2786 ****
  The argument @var{count} is a repeat count; @var{kbdmacro} is executed that
  many times.  If @var{count} is omitted or @code{nil}, @var{kbdmacro} is
  executed once.  If it is 0, @var{kbdmacro} is executed over and over until it
! encounters an error or a failing search.  
  
  @xref{Reading One Event}, for an example of using @code{execute-kbd-macro}.
  @end defun
--- 2780,2786 ----
  The argument @var{count} is a repeat count; @var{kbdmacro} is executed that
  many times.  If @var{count} is omitted or @code{nil}, @var{kbdmacro} is
  executed once.  If it is 0, @var{kbdmacro} is executed over and over until it
! encounters an error or a failing search.
  
  @xref{Reading One Event}, for an example of using @code{execute-kbd-macro}.
  @end defun