From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: igc, macOS avoiding signals Date: Tue, 31 Dec 2024 16:31:05 +0200 Message-ID: <868qrvncuu.fsf@gnu.org> References: <799DDBC5-2C14-4476-B1E0-7BA2FE9E7901@toadstyle.org> <87msgdkt29.fsf@gmail.com> <86h66lnjrt.fsf@gnu.org> <868qrxnfrw.fsf@gnu.org> <87a5ccl2zx.fsf@gmail.com> <86o70sm1ts.fsf@gnu.org> <87h66kndfd.fsf@protonmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35504"; mail-complaints-to="usenet@ciao.gmane.io" Cc: eller.helmut@gmail.com, gerd.moellmann@gmail.com, spd@toadstyle.org, emacs-devel@gnu.org To: Pip Cet Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 31 15:31:53 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tSdHl-00097C-71 for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Dec 2024 15:31:53 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tSdH8-0004EO-Ka; Tue, 31 Dec 2024 09:31:15 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tSdH5-0004EB-BA for emacs-devel@gnu.org; Tue, 31 Dec 2024 09:31:12 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tSdH4-00054V-IL; Tue, 31 Dec 2024 09:31:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=sMaAfcoLcZCV9vEbeRIxusQkBMqd25kGpqcKIvQMRqk=; b=NRYc6lF6U3kr UUmVlSdV6OFfrslp4F9Dbmk55NB3VGQ9+XU9XXMC/8KNCF0p0Npg2FC4cj6FoONesNYB7z9PrBdOo otPoci05BGBE4y4GF+LoxC3wIvfHCUOWUt9T8S0vP5xs4BRrX4dhGlZ0WXY8mAWU8bVbEmv2oDhW6 QuC/44fVHvzVEfEZYSyfB4C9HbmliU5WsgxmSf0TQmPq5fGWt5o4qWzszDSRiMdHr0q4BWimFMVzs BxpPiyejncTf6Uy1LnOuBpepDzf/eZM8oh5KDGRj1VwFAfUddn8twBMjgjbHqFL3P0gSSjkJHD+AM FrV0jJmiDPvemfe6hFkZRA==; In-Reply-To: <87h66kndfd.fsf@protonmail.com> (message from Pip Cet on Tue, 31 Dec 2024 14:19:44 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:327514 Archived-At: > Date: Tue, 31 Dec 2024 14:19:44 +0000 > From: Pip Cet > Cc: Helmut Eller , gerd.moellmann@gmail.com, spd@toadstyle.org, emacs-devel@gnu.org > > > Once again, why not ask the MPS folks to give us a callback? Or maybe > > we could try hacking MPS ourselves first, to see if that does the job, > > and ask them then? > > I'm not sure what your suggestion is at this point, sorry. You said in > another email not too long ago that you wanted to improve the current > code by special-casing "simple" signals; I agreed; now you appear to be > saying we should wait for an MPS modification. There are several possible alternative ways of solving these issues. Moreover, it could be that we prefer different solutions for different signals. A callback, if MPS would let us have it, could allow delaying the signal processing (or most of it) till we are safe to touch data.