From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Allow inserting non-BMP characters Date: Thu, 28 Dec 2017 18:29:00 +0200 Message-ID: <834loahl4j.fsf@gnu.org> References: <20171225210115.13789-1-phst@google.com> <83d132hz9e.fsf@gnu.org> <834lodii55.fsf@gnu.org> <83zi65grxv.fsf@gnu.org> <20171226213642.GB82103@breton.holly.idiocy.org> <83shbwhm70.fsf@gnu.org> <20171228113820.GA83324@breton.holly.idiocy.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1514478449 18154 195.159.176.226 (28 Dec 2017 16:27:29 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 28 Dec 2017 16:27:29 +0000 (UTC) Cc: phst@google.com, alan@idiocy.org, emacs-devel@gnu.org To: Philipp Stephani Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 28 17:27:24 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eUb1d-00049q-9q for ged-emacs-devel@m.gmane.org; Thu, 28 Dec 2017 17:27:21 +0100 Original-Received: from localhost ([::1]:56951 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eUb3c-0006Cl-7a for ged-emacs-devel@m.gmane.org; Thu, 28 Dec 2017 11:29:24 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59455) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eUb31-0006CI-OL for emacs-devel@gnu.org; Thu, 28 Dec 2017 11:28:48 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eUb2y-0006H4-Ki for emacs-devel@gnu.org; Thu, 28 Dec 2017 11:28:47 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:56385) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eUb2y-0006Gq-Gd; Thu, 28 Dec 2017 11:28:44 -0500 Original-Received: from [176.228.60.248] (port=1801 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eUb2x-0003l3-VN; Thu, 28 Dec 2017 11:28:44 -0500 In-reply-to: (message from Philipp Stephani on Thu, 28 Dec 2017 12:31:39 +0000) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:221442 Archived-At: > From: Philipp Stephani > Date: Thu, 28 Dec 2017 12:31:39 +0000 > Cc: phst@google.com, Eli Zaretskii , emacs-devel@gnu.org > > Alan Third schrieb am Do., 28. Dez. 2017 um 12:38 Uhr: > > On Wed, Dec 27, 2017 at 05:41:23AM +0200, Eli Zaretskii wrote: > > What about the possibility that SAFE_NALLOCA could signal an error and > > longjmp to top level? Does this code always run in the main thread, > > and if so, can it allow such longjmp's? > > I think it does always run in the main thread, however since it runs > within the NSApplication run loop I’ve no idea what would happen if we > did a longjmp. > > We should probably avoid longjmps here. This message is invoked by the window manager, which most likely > can't deal with longjmps. Then maybe process the input in chunks using a fixed-size buffer?