unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: bug#54667: 29.0.50; posix_spawn breaks emacs-gdb
Date: Wed, 06 Apr 2022 14:09:04 +0300	[thread overview]
Message-ID: <83o81ecvu7.fsf@gnu.org> (raw)
In-Reply-To: <87pmlu60vf.fsf@gmail.com> (message from Robert Pluim on Wed, 06 Apr 2022 11:02:12 +0200)

> From: Robert Pluim <rpluim@gmail.com>
> Date: Wed, 06 Apr 2022 11:02:12 +0200
> 
> >>>>> On Mon, 04 Apr 2022 16:11:51 +0200, Robert Pluim <rpluim@gmail.com> said:
>     Robert> In emacs-28 we only use posix_spawn on macOS because its vork is
>     Robert> sub-optimal. I donʼt remember the rationale for switching to using it
>     Robert> everywhere, itʼs undoubtedly in the archives somewhere.
> 
>     Robert> Closing.
>     Robert> Committed as 8103b060d8
> 
> Actually, do we want this in emacs-28 as well?

The fix installed on master isn't macOS-specific, AFAICT.  Can it be
reasonably installed on emacs-28 as macOS-specific?  If yes, I think
we should indeed backport it.

Thanks.



  reply	other threads:[~2022-04-06 11:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f26aa6b4-654d-dbba-4e6f-4c71a03e3d5a@gmail.com>
     [not found] ` <87fsmx80e5.fsf@gmail.com>
     [not found]   ` <4d6ef0f6-8ab6-2dce-aa63-d18108fd5f21@gmail.com>
     [not found]     ` <87bkxk983m.fsf@gmail.com>
     [not found]       ` <87ilrp6iqg.fsf@gmail.com>
2022-04-06  9:02         ` bug#54667: 29.0.50; posix_spawn breaks emacs-gdb Robert Pluim
2022-04-06 11:09           ` Eli Zaretskii [this message]
2022-04-06 12:04             ` Robert Pluim
2022-04-06 12:21               ` Eli Zaretskii
2022-04-06 12:33                 ` Robert Pluim
2022-04-06 15:48                   ` Eli Zaretskii
2022-04-07 11:10                     ` Robert Pluim

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=83o81ecvu7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@gmail.com \
    /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).