unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: charles@aurox.ch (Charles A. Roelli)
To: charles@aurox.ch
Cc: 33191@debbugs.gnu.org
Subject: bug#33191: 26.1.50; remove remaining process input batching doc
Date: Sun, 09 Dec 2018 11:45:26 +0100	[thread overview]
Message-ID: <m2k1kjx9kp.fsf@aurox.ch> (raw)
In-Reply-To: <m2k1m1zw59.fsf@aurox.ch> (charles@aurox.ch)

> Date: Sun, 28 Oct 2018 20:52:34 +0100
> From: charles@aurox.ch (Charles A. Roelli)
> 
> (as discussed in Bug#33050#116)
> 
> - Remove mention of "stray character injections" in Elisp node
>   "Asynchronous Processes".
> - Remove doc of "process-send-string" and "process-send-region" 
>   claiming to split process input every 500 characters.

Here's a suggested change for emacs-26:

diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi
index e7d61bd..623be09 100644
--- a/doc/lispref/processes.texi
+++ b/doc/lispref/processes.texi
@@ -604,10 +604,9 @@ Asynchronous Processes
 internal purposes (i.e., no user interaction with the subprocess is
 required), where significant amounts of data need to be exchanged
 between the subprocess and the Lisp program, it is often better to use
-a pipe, because pipes are more efficient, and because they are immune
-to stray character injections that ptys introduce for large (around
-500 byte) messages.  Also, the total number of ptys is limited on many
-systems, and it is good not to waste them unnecessarily.
+a pipe, because pipes are more efficient.  Also, the total number of
+ptys is limited on many systems, and it is good not to waste them
+unnecessarily.
 
 @defun make-process &rest args
 This function is the basic low-level primitive for starting
diff --git a/src/process.c b/src/process.c
index b0a3272..90e0f64 100644
--- a/src/process.c
+++ b/src/process.c
@@ -6456,9 +6456,6 @@ DEFUN ("process-send-region", Fprocess_send_region, Sprocess_send_region,
 PROCESS may be a process, a buffer, the name of a process or buffer, or
 nil, indicating the current buffer's process.
 Called from program, takes three arguments, PROCESS, START and END.
-If the region is more than 500 characters long,
-it is sent in several bunches.  This may happen even for shorter regions.
-Output from processes can arrive in between bunches.
 
 If PROCESS is a non-blocking network process that hasn't been fully
 set up yet, this function will block until socket setup has completed.  */)
@@ -6489,9 +6486,6 @@ DEFUN ("process-send-string", Fprocess_send_string, Sprocess_send_string,
        doc: /* Send PROCESS the contents of STRING as input.
 PROCESS may be a process, a buffer, the name of a process or buffer, or
 nil, indicating the current buffer's process.
-If STRING is more than 500 characters long,
-it is sent in several bunches.  This may happen even for shorter strings.
-Output from processes can arrive in between bunches.
 
 If PROCESS is a non-blocking network process that hasn't been fully
 set up yet, this function will block until socket setup has completed.  */)






  reply	other threads:[~2018-12-09 10:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28 19:52 bug#33191: 26.1.50; remove remaining process input batching doc Charles A. Roelli
2018-12-09 10:45 ` Charles A. Roelli [this message]
2018-12-09 12:47   ` Eli Zaretskii
2018-12-09 16:15     ` Charles A. Roelli
2018-12-09 16:32       ` Eli Zaretskii
2018-12-09 19:24         ` Charles A. Roelli
2018-12-22 10:53           ` Eli Zaretskii
2018-12-22 16:17             ` Charles A. Roelli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2k1kjx9kp.fsf@aurox.ch \
    --to=charles@aurox.ch \
    --cc=33191@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).