From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24531@debbugs.gnu.org, sbaugh@janestreet.com,
6149@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#24531: bug#6149: bug#24531: process-send-string seems to truncate lines over 4096 characters
Date: Fri, 21 Jul 2023 11:09:17 -0400 [thread overview]
Message-ID: <jwva5vpnw14.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83sf9h257b.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 21 Jul 2023 08:39:52 +0300")
>> Also I don't think either value of `process-connection-type` is a good
>> option. IOW, I think that the connection type should be a mandatory
>> argument when creating an async process (except maybe for those
>> processes with no input/output).
> If we go that way, we should start by specifying :connection-type for
> all the uses of make-process and start-process we have in the core.
That would be a good start, yes.
Stefan
next prev parent reply other threads:[~2023-07-21 15:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 4:14 bug#6149: 24.0.50; shell buffer overflow when input longer than 4096 bytes jidanni
2010-06-01 1:50 ` Stefan Monnier
2023-07-20 20:15 ` bug#6149: bug#24531: process-send-string seems to truncate lines over 4096 characters Spencer Baugh
2023-07-20 21:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-21 5:39 ` Eli Zaretskii
2023-07-21 13:58 ` Spencer Baugh
2023-07-21 14:18 ` Eli Zaretskii
2023-07-27 1:48 ` bug#6149: " Dmitry Gutov
2023-07-27 5:41 ` Eli Zaretskii
2023-07-27 13:59 ` Spencer Baugh
2023-07-27 14:51 ` Paul Eggert
2023-07-21 15:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2018-09-28 20:13 ` bug#6149: 24.0.50; shell buffer overflow when input longer than 4096 bytes 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=jwva5vpnw14.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=24531@debbugs.gnu.org \
--cc=6149@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.org \
--cc=monnier@iro.umontreal.ca \
--cc=sbaugh@janestreet.com \
/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).