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, 15 May 2021 10:23:10 +0300 [thread overview]
Message-ID: <83fsyoxxy9.fsf@gnu.org> (raw)
In-Reply-To: <daa66cd4-dfec-6dd3-efe9-ca35dca8a391@ims.co.at> (message from Thomas Hisch on Fri, 7 May 2021 21:46:15 +0200)
> Date: Fri, 7 May 2021 21:46:15 +0200
> From: Thomas Hisch <thomas.hisch@ims.co.at>
> CC: <48129@debbugs.gnu.org>
>
> >> 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?
> >>
> >
> > Thx Eli for the fast reply! I had to study the docs of make-pipe-process
> > and make-process to understand what you mean. However, I'm not fully
> > sure if I fully get what you mean.
> >
> > AFAICS the pipe process which is returned by make-pipe-process can be
> > passed to the :stderr keyword argument of make-process. Is that what you
> > head in mind?
> >
> > According to the docs of make-process, process-connection-type is
> > ignored if :stderr is passed to make-process:
> >
> >> This parameter and the value of ‘process-connection-type’ are
> > ignored if a non-‘nil’ value is specified for the ‘:stderr’ parameter;
> > in that case, the type will always be ‘pipe’.
> >
> > What I want is that stdout and stderr are connected to a pipe but stdin
> > is connected to a pty.
> >
> > Here is the new test script that I used
> >
> > (let* (
> > (stderr-buffer (get-buffer-create "*stderr*"))
> > (stderr-proc (make-pipe-process :name "stderr"
> > :buffer stderr-buffer))
> > (process-buf (get-buffer-create "*temp*")))
> > (make-process
> > :name "isatty"
> > :buffer process-buf ;; it is not possible to pass the output of
> > make-pipe-process to :buffer
> > :connection-type 'pty ;; unfortunately ignored if :stderr is used
> > :stderr stderr-proc
> > :command (list "/tmp/output-isatty.py")))
> >
>
> Eli can you tell me if you meant that we should use make-process in
> combination with make-pipe-process?
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.
next prev parent reply other threads:[~2021-05-15 7:23 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
2021-05-02 10:19 ` Thomas Hisch
2021-05-07 19:46 ` Thomas Hisch
2021-05-15 7:23 ` Eli Zaretskii [this message]
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=83fsyoxxy9.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).