[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/lispref/processes.texi
From: |
Juanma Barranquero |
Subject: |
[Emacs-diffs] Changes to emacs/lispref/processes.texi |
Date: |
Tue, 02 Aug 2005 09:10:02 -0400 |
Index: emacs/lispref/processes.texi
diff -c emacs/lispref/processes.texi:1.65 emacs/lispref/processes.texi:1.66
*** emacs/lispref/processes.texi:1.65 Sat Jun 18 13:55:48 2005
--- emacs/lispref/processes.texi Tue Aug 2 13:10:02 2005
***************
*** 1575,1581 ****
process, being stopped means not accepting new connections. (Up to 5
connection requests will be queued for when you resume the server; you
can increase this limit, unless it is imposed by the operating
! systems.) For a network stream connection, being stopped means not
processing input (any arriving input waits until you resume the
connection). For a datagram connection, some number of packets may be
queued but input may be lost. You can use the function
--- 1575,1581 ----
process, being stopped means not accepting new connections. (Up to 5
connection requests will be queued for when you resume the server; you
can increase this limit, unless it is imposed by the operating
! system.) For a network stream connection, being stopped means not
processing input (any arriving input waits until you resume the
connection). For a datagram connection, some number of packets may be
queued but input may be lost. You can use the function
- [Emacs-diffs] Changes to emacs/lispref/processes.texi,
Juanma Barranquero <=