unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Thomas Hisch <thomas.hisch@ims.co.at>
Cc: 48129@debbugs.gnu.org
Subject: bug#48129: 28.0.50; Per file-handle (stdin, stdout and stderr) process-connection-type variable
Date: Sat, 01 May 2021 09:09:39 +0300	[thread overview]
Message-ID: <83o8dv9e8s.fsf@gnu.org> (raw)
In-Reply-To: <yedk0oje5d9.fsf@ims.co.at> (message from Thomas Hisch on Sat, 1 May 2021 01:10:10 +0200)

> From: Thomas Hisch <thomas.hisch@ims.co.at>
> Date: Sat, 1 May 2021 01:10:10 +0200
> 
> 
> I would like that the configuration options of the three file
> handles (stdin, stdout and stderr), when a new process is created
> in emacs, are improved.  What I'm specifically asking for is to
> add support for individually specifying for each file-handle
> whether it should be connected to a pty or not.  Currently the
> value of the process-connection-type variable applies to all
> three file handles at once, which leads to a problem with the
> following use-case:
> 
> Usually a program outputs ANSI escape sequences when its stdout
> file-handle is connected to a pty. It is currently not possible to
> communicate with a subprocess that is created by `start-file-process' by
> writing to a pty (via stdin) and avoiding that this subprocess writes
> ANSI escape sequences to stdout. This use-case is needed by magit, which
> currently doesn't have support for displaying ANSI escape sequences but
> it needs to communicate with it's started subprocesses via a PTY
> (https://github.com/magit/magit/issues/3549).

We have make-pipe-process; can't you solve your problem by connecting
your process's stdout to such a pipe-process?  If not, why not?





  reply	other threads:[~2021-05-01  6:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 23:10 bug#48129: 28.0.50; Per file-handle (stdin, stdout and stderr) process-connection-type variable Thomas Hisch
2021-05-01  6:09 ` Eli Zaretskii [this message]
2021-05-02 10:19   ` Thomas Hisch
2021-05-07 19:46     ` Thomas Hisch
2021-05-15  7:23       ` Eli Zaretskii
2021-06-12 12:18         ` Lars Ingebrigtsen
2021-06-12 14:23           ` Thomas Hisch
2021-06-12 15:31             ` Eli Zaretskii
2021-06-12 16:49               ` Thomas Hisch
2021-06-12 15:48             ` Lars Ingebrigtsen

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=83o8dv9e8s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=48129@debbugs.gnu.org \
    --cc=thomas.hisch@ims.co.at \
    /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).