From: Eli Zaretskii <eliz@gnu.org>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: 33050@debbugs.gnu.org, fitzsim@fitzsim.org, alan@idiocy.org
Subject: bug#33050: 27.0.50; [macOS] Problem with process input with process-connection-type nil
Date: Sat, 27 Oct 2018 09:59:46 +0300 [thread overview]
Message-ID: <83k1m3oowt.fsf@gnu.org> (raw)
In-Reply-To: <m2bm7gti96.fsf@fgunbin.playteam.ru> (message from Filipp Gunbin on Sat, 27 Oct 2018 02:12:21 +0300)
> From: Filipp Gunbin <fgunbin@fastmail.fm>
> Cc: Eli Zaretskii <eliz@gnu.org>, 33050@debbugs.gnu.org, alan@idiocy.org
> Date: Sat, 27 Oct 2018 02:12:21 +0300
>
> Thomas,
I'm not him, but since you asked...
> I don't really understand why pty mode is better here than pipe mode.
> Do we need job control, or escape sequences, or anything else specific
> to pty?
Yes, we want the buffering be as if ldapsearch was invoked from a
terminal. Possibly also other features, but I don't know enough about
the program to tell.
Basically, if the program was written for interactive invocation
communicating through pty is always better.
> If we use pty, won't these features, on the contrary, get in
> the way somewhere?
If they get in the way, it's another bug, which needs to be analyzed
and solved. It could be (although IMO improbable) that we decide to
go back to pipes, but then we will know why we did that, and we should
leave behind a comment with the explanation.
> Your suggestion to condionally fix this for Darwin on release looks
> good.
Right.
next prev parent reply other threads:[~2018-10-27 6:59 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 19:03 bug#33050: 27.0.50; [macOS] Problem with process input with process-connection-type nil Filipp Gunbin
2018-10-20 10:09 ` Eli Zaretskii
2018-10-22 15:35 ` Filipp Gunbin
2018-10-23 1:53 ` Thomas Fitzsimmons
2018-10-23 22:41 ` Filipp Gunbin
2018-10-24 1:55 ` Thomas Fitzsimmons
2018-10-24 13:13 ` Filipp Gunbin
2018-10-24 14:05 ` Filipp Gunbin
2018-10-24 16:20 ` Thomas Fitzsimmons
2018-10-24 19:33 ` Filipp Gunbin
2018-10-24 19:46 ` Filipp Gunbin
2018-10-24 22:07 ` Thomas Fitzsimmons
2018-10-25 15:51 ` Filipp Gunbin
2018-10-25 16:24 ` Eli Zaretskii
2018-10-25 17:10 ` Filipp Gunbin
2018-10-25 17:29 ` Eli Zaretskii
2018-10-25 18:10 ` Filipp Gunbin
2018-10-25 18:20 ` Eli Zaretskii
2018-10-25 19:36 ` Filipp Gunbin
2018-10-25 19:40 ` Eli Zaretskii
2018-10-25 20:47 ` Filipp Gunbin
2018-10-26 6:29 ` Eli Zaretskii
2018-10-26 1:41 ` Thomas Fitzsimmons
2018-10-26 7:00 ` Eli Zaretskii
2018-10-26 15:41 ` Thomas Fitzsimmons
2018-10-26 17:20 ` Eli Zaretskii
2018-10-27 10:20 ` Eli Zaretskii
2018-10-27 13:42 ` Thomas Fitzsimmons
2018-10-27 14:53 ` Eli Zaretskii
2018-10-27 16:53 ` Thomas Fitzsimmons
2018-10-27 18:49 ` Eli Zaretskii
2018-10-26 23:12 ` Filipp Gunbin
2018-10-27 2:09 ` Thomas Fitzsimmons
2018-10-27 14:52 ` Filipp Gunbin
2018-10-30 0:49 ` Thomas Fitzsimmons
2018-10-30 19:11 ` Filipp Gunbin
2018-11-28 23:09 ` Filipp Gunbin
2018-11-29 7:21 ` Eli Zaretskii
2018-11-29 8:46 ` Filipp Gunbin
2018-11-29 9:19 ` Eli Zaretskii
2018-11-29 9:51 ` Filipp Gunbin
2018-11-29 10:41 ` Eli Zaretskii
2018-11-29 14:09 ` Filipp Gunbin
2018-12-03 14:17 ` Thomas Fitzsimmons
2018-12-04 12:37 ` Filipp Gunbin
2018-12-22 15:05 ` Thomas Fitzsimmons
2018-10-27 6:59 ` Eli Zaretskii [this message]
2018-10-27 14:37 ` Filipp Gunbin
2018-10-27 20:28 ` Charles A. Roelli
2018-10-28 16:00 ` Eli Zaretskii
2018-10-28 19:53 ` Charles A. Roelli
2018-10-25 16:41 ` Filipp Gunbin
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=83k1m3oowt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33050@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=fgunbin@fastmail.fm \
--cc=fitzsim@fitzsim.org \
/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.