From: Paul Eggert <eggert@cs.ucla.edu>
To: Filipp Gunbin <fgunbin@fastmail.fm>,
Andreas Schwab <schwab@linux-m68k.org>
Cc: Alan Third <alan@idiocy.org>, 33154@debbugs.gnu.org
Subject: bug#33154: 27.0.50; create_process on Darwin should not invoke setsid() after vfork() [PATCH]
Date: Sat, 10 Nov 2018 09:09:14 -0800 [thread overview]
Message-ID: <214f349a-d95d-823a-3461-6facd9cbfbbf@cs.ucla.edu> (raw)
In-Reply-To: <m24lcp551k.fsf@fastmail.fm>
Filipp Gunbin wrote:
> On 09/11/2018 12:16 +0100, Andreas Schwab wrote:
>
>> On Nov 09 2018, Filipp Gunbin <fgunbin@fastmail.fm> wrote:
>>
>>> I have one failing case: "M-x shell-command sudo ls -la" reports "sudo:
>>> no tty present and no askpass program specified".
>>
>> That's not a bug. If shell-command runs the command synchronously it
>> doesn't allocate a tty.
>
> Are there any reasons for not allocating a pty in this case? A
> synchronous program may be interactive.
How would the interaction work, though? I can see potential problems with
existing Lisp code that runs synchronous commands if we allocate ptys for them.
At any rate, that case has always failed the same way on Ubuntu 18.04 etc., so
if this is a problem it's not limited to macOS and someone should file a new bug
report for it.
next prev parent reply other threads:[~2018-11-10 17:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 19:30 bug#33154: 27.0.50; create_process on Darwin should not invoke setsid() after vfork() [PATCH] Filipp Gunbin
2018-10-26 11:12 ` Alan Third
2018-11-07 1:35 ` Filipp Gunbin
2018-11-05 17:28 ` Paul Eggert
2018-11-06 13:46 ` Filipp Gunbin
2018-11-07 1:23 ` Filipp Gunbin
2018-11-07 7:41 ` Paul Eggert
2018-11-07 8:53 ` Filipp Gunbin
2018-11-07 15:40 ` Paul Eggert
2018-11-09 0:07 ` Alan Third
2018-11-09 10:29 ` Filipp Gunbin
2018-11-09 11:16 ` Andreas Schwab
2018-11-10 15:24 ` Filipp Gunbin
2018-11-10 17:09 ` Paul Eggert [this message]
2018-11-11 17:14 ` Filipp Gunbin
2018-11-10 17:05 ` Paul Eggert
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=214f349a-d95d-823a-3461-6facd9cbfbbf@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=33154@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=fgunbin@fastmail.fm \
--cc=schwab@linux-m68k.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 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).