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

[Richard M . Stallman]

Index: emacs/lispref/processes.texi
diff -c emacs/lispref/processes.texi:1.68 emacs/lispref/processes.texi:1.69
*** emacs/lispref/processes.texi:1.68   Thu Aug 11 19:46:35 2005
--- emacs/lispref/processes.texi        Mon Oct 17 16:16:27 2005
***************
*** 1096,1104 ****
  
    Quitting is normally inhibited within a filter function---otherwise,
  the effect of typing @kbd{C-g} at command level or to quit a user
! command would be unpredictable.  If you want to permit quitting inside a
! filter function, bind @code{inhibit-quit} to @code{nil}.
! @xref{Quitting}.
  
    If an error happens during execution of a filter function, it is
  caught automatically, so that it doesn't stop the execution of whatever
--- 1096,1105 ----
  
    Quitting is normally inhibited within a filter function---otherwise,
  the effect of typing @kbd{C-g} at command level or to quit a user
! command would be unpredictable.  If you want to permit quitting inside
! a filter function, bind @code{inhibit-quit} to @code{nil}.  In most
! cases, the right way to do this is with the macro
! @code{with-local-quit}.  @xref{Quitting}.
  
    If an error happens during execution of a filter function, it is
  caught automatically, so that it doesn't stop the execution of whatever
***************
*** 1375,1389 ****
  termination will always run the sentinel exactly once.  This is
  because the process status can't change again after termination.
  
!   Quitting is normally inhibited within a sentinel---otherwise, the
! effect of typing @kbd{C-g} at command level or to quit a user command
! would be unpredictable.  If you want to permit quitting inside a
! sentinel, bind @code{inhibit-quit} to @code{nil}.  @xref{Quitting}.
  
    A sentinel that writes the output into the buffer of the process
  should check whether the buffer is still alive.  If it tries to insert
  into a dead buffer, it will get an error.  If the buffer is dead,
  @code{(buffer-name (process-buffer @var{process}))} returns @code{nil}.
  
    If an error happens during execution of a sentinel, it is caught
  automatically, so that it doesn't stop the execution of whatever
--- 1376,1396 ----
  termination will always run the sentinel exactly once.  This is
  because the process status can't change again after termination.
  
!   Emacs explicitly checks for output from the process before running
! the process sentinel.  Once the sentinel runs due to process
! termination, no further output can arrive from the process.
  
    A sentinel that writes the output into the buffer of the process
  should check whether the buffer is still alive.  If it tries to insert
  into a dead buffer, it will get an error.  If the buffer is dead,
  @code{(buffer-name (process-buffer @var{process}))} returns @code{nil}.
+ 
+   Quitting is normally inhibited within a sentinel---otherwise, the
+ effect of typing @kbd{C-g} at command level or to quit a user command
+ would be unpredictable.  If you want to permit quitting inside a
+ sentinel, bind @code{inhibit-quit} to @code{nil}.  In most cases, the
+ right way to do this is with the macro @code{with-local-quit}.
+ @xref{Quitting}.
  
    If an error happens during execution of a sentinel, it is caught
  automatically, so that it doesn't stop the execution of whatever