/[emacs]/emacs/lispref/processes.texi
ViewVC logotype

Diff of /emacs/lispref/processes.texi

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.68 by rms, Thu Aug 11 19:46:35 2005 UTC revision 1.69 by rms, Mon Oct 17 16:16:27 2005 UTC
# Line 1096  then free to do whatever it chooses with Line 1096  then free to do whatever it chooses with
1096    
1097    Quitting is normally inhibited within a filter function---otherwise,    Quitting is normally inhibited within a filter function---otherwise,
1098  the effect of typing @kbd{C-g} at command level or to quit a user  the effect of typing @kbd{C-g} at command level or to quit a user
1099  command would be unpredictable.  If you want to permit quitting inside a  command would be unpredictable.  If you want to permit quitting inside
1100  filter function, bind @code{inhibit-quit} to @code{nil}.  a filter function, bind @code{inhibit-quit} to @code{nil}.  In most
1101  @xref{Quitting}.  cases, the right way to do this is with the macro
1102    @code{with-local-quit}.  @xref{Quitting}.
1103    
1104    If an error happens during execution of a filter function, it is    If an error happens during execution of a filter function, it is
1105  caught automatically, so that it doesn't stop the execution of whatever  caught automatically, so that it doesn't stop the execution of whatever
# Line 1375  quick succession, can call the sentinel Line 1376  quick succession, can call the sentinel
1376  termination will always run the sentinel exactly once.  This is  termination will always run the sentinel exactly once.  This is
1377  because the process status can't change again after termination.  because the process status can't change again after termination.
1378    
1379    Quitting is normally inhibited within a sentinel---otherwise, the    Emacs explicitly checks for output from the process before running
1380  effect of typing @kbd{C-g} at command level or to quit a user command  the process sentinel.  Once the sentinel runs due to process
1381  would be unpredictable.  If you want to permit quitting inside a  termination, no further output can arrive from the process.
 sentinel, bind @code{inhibit-quit} to @code{nil}.  @xref{Quitting}.  
1382    
1383    A sentinel that writes the output into the buffer of the process    A sentinel that writes the output into the buffer of the process
1384  should check whether the buffer is still alive.  If it tries to insert  should check whether the buffer is still alive.  If it tries to insert
1385  into a dead buffer, it will get an error.  If the buffer is dead,  into a dead buffer, it will get an error.  If the buffer is dead,
1386  @code{(buffer-name (process-buffer @var{process}))} returns @code{nil}.  @code{(buffer-name (process-buffer @var{process}))} returns @code{nil}.
1387    
1388      Quitting is normally inhibited within a sentinel---otherwise, the
1389    effect of typing @kbd{C-g} at command level or to quit a user command
1390    would be unpredictable.  If you want to permit quitting inside a
1391    sentinel, bind @code{inhibit-quit} to @code{nil}.  In most cases, the
1392    right way to do this is with the macro @code{with-local-quit}.
1393    @xref{Quitting}.
1394    
1395    If an error happens during execution of a sentinel, it is caught    If an error happens during execution of a sentinel, it is caught
1396  automatically, so that it doesn't stop the execution of whatever  automatically, so that it doesn't stop the execution of whatever
1397  programs was running when the sentinel was started.  However, if  programs was running when the sentinel was started.  However, if

Legend:
Removed from v.1.68  
changed lines
  Added in v.1.69

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26