GNU bug report logs - #48129
28.0.50; Per file-handle (stdin, stdout and stderr) process-connection-type variable

Previous Next

Full log

Message #27 received at 48129 <at> debbugs.gnu.org (full text, mbox):

From: Thomas Hisch <thomas.hisch <at> ims.co.at>
To: Lars Ingebrigtsen <larsi <at> gnus.org>, Eli Zaretskii <eliz <at> gnu.org>
Cc: 48129 <at> debbugs.gnu.org
Subject: Re: bug#48129: 28.0.50; Per file-handle (stdin, stdout and stderr)
 process-connection-type variable
Date: Sat, 12 Jun 2021 16:23:29 +0200

Hi,

On 6/12/21 14:18, Lars Ingebrigtsen wrote:
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>> If it's possible to solve your problem by using make-pipe-process, I'd
>> prefer such a solution.  Introducing yet another obscure option to
>> make-process should best be avoided, IMO.

Yes I agree, if I could use make-pipe-process I would use it, but I
guess it doesn't work.


(let* ((stderr-buffer (get-buffer-create "*stderr*"))
       (stderr-pipe-proc (make-pipe-process :name "stderr"
                                            :buffer stderr-buffer))
       (stdout-buffer (get-buffer-create "*temp*")))
    (make-process
     :name "isatty"
     ;; what do I want?
     ;; I want stdin to be connected to a pty but not stdout
     :buffer stdout-buffer
     :connection-type 'pty
     :stderr stderr-pipe-proc
     :command (list "/tmp/output-isatty.py")))

What have I tried:

* toggling the connection-type arguement doesn't have any impact on the
output of the python script, which is run as a subprocess.

* if a stderr argument is passed to make-process and the value is a the
pipe-process, then both stdin as well as stdout in the subprocess are
connected non-pty devices

* if a stderr argument is not passed to make-process, then both stdin as
well as stdout in the subprocess are connected to pty devices.


Can you tell me if I should use make-process/make-pipe-process in a
different way?


> This was a month ago, and there was no followup, so I'm going to go
> ahead and assume that the make-pipe-process workaround works (and that
> seems like a pretty composable solution to me, too), and I'm closing
> this bug report.
>
> If there's more to be done here, please respond to the debbugs address
> and we'll reopen.
>

sry for the late reply. Unfortunately make-pike-process doesn't work for
me, or at least I don't know how I should use it.



Best regards,
Thomas




Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly prohibited.

IMS Nanofabrication GmbH FN: 208021 p, FB-Gericht: Wien; Sitz: Schreygasse 3, 1020, Vienna (Austria),Tel. +43 1 214 48 94; E-Mail: imsoffice <at> ims.co.at; DVR-Nr: 0374369; www.ims.co.at

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.