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: Can we go GTK-only? Date: Tue, 01 Nov 2016 19:44:16 +0200 Message-ID: <83bmxznlhr.fsf@gnu.org> References: <24db2975-17ca-ad01-20c8-df12071fa89a@dancol.org> <4615E73A-19E2-4B79-9889-D3FA686DDDE6@raeburn.org> <83bmy0pl8p.fsf@gnu.org> <831sywp7ew.fsf@gnu.org> <83y413nsjm.fsf@gnu.org> <83funbnngl.fsf@gnu.org> <83d1ifnmto.fsf@gnu.org> <5a860f84-bb7e-38e0-fc10-c9d794382b79@dancol.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1478022686 2167 195.159.176.226 (1 Nov 2016 17:51:26 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 1 Nov 2016 17:51:26 +0000 (UTC) Cc: raeburn@raeburn.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 01 18:51:18 2016 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 1c1dD1-00058A-0O for ged-emacs-devel@m.gmane.org; Tue, 01 Nov 2016 18:50:51 +0100 Original-Received: from localhost ([::1]:49857 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1dD3-0001lf-Lc for ged-emacs-devel@m.gmane.org; Tue, 01 Nov 2016 13:50:53 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43448) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1d6T-00053J-QO for emacs-devel@gnu.org; Tue, 01 Nov 2016 13:44:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c1d6Q-0006yF-Pc for emacs-devel@gnu.org; Tue, 01 Nov 2016 13:44:05 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:42314) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1d6Q-0006xz-Mp; Tue, 01 Nov 2016 13:44:02 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4217 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1c1d6P-0005zg-QQ; Tue, 01 Nov 2016 13:44:02 -0400 In-reply-to: <5a860f84-bb7e-38e0-fc10-c9d794382b79@dancol.org> (message from Daniel Colascione on Tue, 1 Nov 2016 10:18:58 -0700) 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:209074 Archived-At: > Cc: raeburn@raeburn.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org > From: Daniel Colascione > Date: Tue, 1 Nov 2016 10:18:58 -0700 > > > CPU-intensive threads that cannot manipulate Lisp objects (not run > > Lisp, but create and destroy Lisp objects) are not very useful in > > Emacs. > > Redisplay itself can run without invoking Lisp _most_ of the time No, it can't. It calls Lisp almost all the time. The two main places where that usually happens is JIT font-lock and mode-line display. Maybe you are thinking about "emacs -Q" which is idle, but that's not a very interesting use case, when multi-threading is being discussed. I don't want to argue about your other arguments because I don't see a point.