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: Should this package be included into the NS port? Date: Thu, 24 May 2018 21:14:55 +0300 Message-ID: <83y3g8apk0.fsf@gnu.org> References: <20180515183631.GB27909@breton.holly.idiocy.org> <20180518193632.GA31241@breton.holly.idiocy.org> <20180519103329.GB31853@breton.holly.idiocy.org> <83k1rucs15.fsf@gnu.org> <20180523212129.GB36578@breton.holly.idiocy.org> <83h8mxau22.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1527185571 29544 195.159.176.226 (24 May 2018 18:12:51 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 24 May 2018 18:12:51 +0000 (UTC) Cc: alan@idiocy.org, nick@tenpoint.co.nz, emacs-devel@gnu.org, georgedp@orbitalimpact.com, monnier@iro.umontreal.ca To: Philipp Stephani Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 24 20:12:46 2018 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 1fLujF-0007X6-61 for ged-emacs-devel@m.gmane.org; Thu, 24 May 2018 20:12:45 +0200 Original-Received: from localhost ([::1]:40143 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fLulM-0006zk-A3 for ged-emacs-devel@m.gmane.org; Thu, 24 May 2018 14:14:56 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35450) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fLulF-0006zT-IF for emacs-devel@gnu.org; Thu, 24 May 2018 14:14:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fLulB-0004EB-Jz for emacs-devel@gnu.org; Thu, 24 May 2018 14:14:49 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:40360) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fLulB-0004E7-F6; Thu, 24 May 2018 14:14:45 -0400 Original-Received: from [176.228.60.248] (port=4154 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fLulA-0000A5-UN; Thu, 24 May 2018 14:14:45 -0400 In-reply-to: (message from Philipp Stephani on Thu, 24 May 2018 19:46:19 +0200) 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:225673 Archived-At: > From: Philipp Stephani > Date: Thu, 24 May 2018 19:46:19 +0200 > Cc: Alan Third , nick@tenpoint.co.nz, georgedp@orbitalimpact.com, > monnier@iro.umontreal.ca, emacs-devel@gnu.org > > What's the "input thread" in the Windows implementation? Not sure what kind of answer did you want to that. You can find an overview of how this stuff works in the w32 port around line 3250 of w32fns.c; the "input thread" I alluded to is the one that runs the message pump and the related window proc function. > At least on macOS the UI thread (i.e. the thread > that creates windows and handles events) must be the main thread, which means the Lisp interpreter thread > (s) should become background threads. There's no such limitation on Windows, so the main thread runs Lisp.