all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Max Arnold <arnold.maxim@gmail.com>
Cc: 67510@debbugs.gnu.org
Subject: bug#67510: 29.1; macOS accept-process-output line length limit of 1024
Date: Tue, 28 Nov 2023 17:43:37 +0200	[thread overview]
Message-ID: <834jh5993q.fsf@gnu.org> (raw)
In-Reply-To: <CAFA3qscyMGB4F19JhN6ZwpwKY8jjNkrqid7mitf5U5o4PUs2Kw@mail.gmail.com> (message from Max Arnold on Tue, 28 Nov 2023 22:22:31 +0700)

> From: Max Arnold <arnold.maxim@gmail.com>
> Date: Tue, 28 Nov 2023 22:22:31 +0700
> 
> Added one line to blacken.el and it looks like the problem is fixed:
> 
> ```
> (let ((process (make-process :name "blacken"
>                                  :command `(,blacken-executable ,@(blacken-call-args))
>                                  :buffer output-buffer
>                                  :stderr error-buffer
>                                  :noquery t
>                                  :connection-type 'pipe  ;;  <-- ADDED
>                                  :sentinel (lambda (process event)))))
> ```
> 
> Does it mean that the bug is not related to Emacs and I should file it against blacken? If so, sorry for
> the noise.

If blacken has no reason to use PTYs, and it can produce large volumes
of output from the process, then yes, it should use pipes for
communications with the sub-process.





  parent reply	other threads:[~2023-11-28 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28  4:14 bug#67510: 29.1; macOS accept-process-output line length limit of 1024 Max Arnold
2023-11-28 14:51 ` Eli Zaretskii
     [not found]   ` <CAFA3qscyMGB4F19JhN6ZwpwKY8jjNkrqid7mitf5U5o4PUs2Kw@mail.gmail.com>
2023-11-28 15:43     ` Eli Zaretskii [this message]
2023-12-25 14:29       ` Stefan Kangas
2023-12-25 15:08         ` Eli Zaretskii
2023-12-25 18:17           ` Stefan Kangas

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

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

  git send-email \
    --in-reply-to=834jh5993q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=67510@debbugs.gnu.org \
    --cc=arnold.maxim@gmail.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.