From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: Can we go GTK-only? Date: Tue, 1 Nov 2016 10:45:49 -0700 Message-ID: <855d433b-b00c-d0d1-6655-a23a34bec29b@dancol.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> <83bmxznlhr.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1478022466 2669 195.159.176.226 (1 Nov 2016 17:47:46 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 1 Nov 2016 17:47:46 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 Cc: raeburn@raeburn.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 01 18:47:41 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 1c1d9i-0006xP-0m for ged-emacs-devel@m.gmane.org; Tue, 01 Nov 2016 18:47:26 +0100 Original-Received: from localhost ([::1]:49787 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1d9k-0006ga-MN for ged-emacs-devel@m.gmane.org; Tue, 01 Nov 2016 13:47:28 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44350) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1d8I-0006en-Ok for emacs-devel@gnu.org; Tue, 01 Nov 2016 13:45:59 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c1d8F-0007hH-MJ for emacs-devel@gnu.org; Tue, 01 Nov 2016 13:45:58 -0400 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:34588) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c1d8F-0007hD-FO; Tue, 01 Nov 2016 13:45:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=QONwRhMX3aFEidwVj+CNdAzuNwQqotFhjkcjW60dYLA=; b=Xk/IVIgCPoS/9iBPGfWl27pn/eY1b9Si6a6Q2Dt69gAiIAGFVM+EhmU2vvclnu+dHn9LETSm1O2Bucn6quWO9o07LZDrsbRah0IeGAf1ASv2iPYuSTuVRAoiB3kaa64JN/YlPpqohMfduKyIeGqbatCpay72uKFzjBA6KGkadVoEVZmlDNgjl5nRqby4bnnXclUItY2KDfFDqocFkw0EBJDXasOiyRXUdr758m7QoknHTo+TIA/jF17gO+SI2J3poGHSAP6ofprYJkxD1x8qSnitixkVgn8yZ8rHbfVqzHulHN9RHtLPbcQCtNsBNOavIdMMFjXJsQ1oiQXy92C8mA==; Original-Received: from c-73-97-199-232.hsd1.wa.comcast.net ([73.97.199.232] helo=[192.168.1.173]) by dancol.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1c1d8D-0004bw-3r; Tue, 01 Nov 2016 10:45:53 -0700 In-Reply-To: <83bmxznlhr.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 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:209072 Archived-At: On 11/01/2016 10:44 AM, Eli Zaretskii wrote: >> 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. Why don't you see a point in buttressing your claims with facts?