From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Emacs design and architecture. How about copy-on-write? Date: Tue, 19 Sep 2023 18:15:50 +0300 Message-ID: <99e84ae7-b3aa-a009-5cb8-a75826343196@gutov.dev> References: <83edizjn0v.fsf@gnu.org> <0518f65b-1dd1-6923-8497-da4d3aeac631@gutov.dev> <87sf7fc7kd.fsf@dataswamp.org> <834jjuk68t.fsf@gnu.org> <87cyyhc7uu.fsf@dataswamp.org> <83ttrsg9nx.fsf@gnu.org> <83h6nrg4eg.fsf@gnu.org> <83v8c7elan.fsf@gnu.org> <877conk5ny.fsf@localhost> <83ttrreeu0.fsf@gnu.org> <87bkdzeas1.fsf@localhost> <83cyyfe5l8.fsf@gnu.org> <87led2o0nb.fsf@localhost> <83ttrqcpfb.fsf@gnu.org> <877comnv4a.fsf@localhost> <83fs3ackrq.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3520"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Cc: acm@muc.de, incal@dataswamp.org, emacs-devel@gnu.org To: Eli Zaretskii , Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Sep 19 17:17:08 2023 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 1qicTI-0000YH-AR for ged-emacs-devel@m.gmane-mx.org; Tue, 19 Sep 2023 17:17:05 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qicSR-0003mC-DP; Tue, 19 Sep 2023 11:16:11 -0400 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 1qicSP-0003lz-51 for emacs-devel@gnu.org; Tue, 19 Sep 2023 11:16:10 -0400 Original-Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qicSH-0002z7-JW; Tue, 19 Sep 2023 11:16:08 -0400 Original-Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 6AC405C009D; Tue, 19 Sep 2023 11:15:54 -0400 (EDT) Original-Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 19 Sep 2023 11:15:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gutov.dev; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1695136554; x=1695222954; bh=/ourqkvG26NikfxPkQfz3Kgy1vC0xGAZZiu DvC3VL48=; b=KEgP1YGEua2W9PD/uSyyACz2ORc1Y95b2sB+AJpelQ+UW4yJPts QJ6Zd0j1TpQxmVEAY/eviB9vJ63/HqewD+v5QaRRglLlhDa5NCYcX9k+NdDpkVpU rZYqpCoETZWc5jEY0SBHbGOk5w1fdbydtLGfNlLl640b42nXeunZXc9hrSITpYcn 8UC+ZIFk/TsCBJeVhbcd2GxMWy/JeLxpqjTmvTGKUp88mYXWSk5D+otXjdda/8qV aeC+mLiC79QSwtMCGG0SVS+0Ms21V+9Dpl53qOrEgK9XD/WpGXIwZH6MUHKX+I7z vo015/tdwNCZIFGZ1DWX1ifKvOZbKqH/oTw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1695136554; x=1695222954; bh=/ourqkvG26NikfxPkQfz3Kgy1vC0xGAZZiu DvC3VL48=; b=fj7wuA8BCEARK2EuSu4kQipF4Y1GtSVkQ94/OAbRfU7eL0xRp/v NlAbm5a4d4Dk3CMy7QvNDF+AwL+ZOqt2WC4jE2ZJW1MrW02u3PzwN34iOTohqgOd 5VTK/MSKZPmaIYzNjV1uXSvrgCIsKH1NhWB2SqBQEfIlyBUS35VTFch7Pl8THkCo V8XLLFHh0bwCZp1Pj/s9eI/OeaHbPrPleAoUalOQCo1/ABSglne4catibXJ3sKfx 9uAZeEhOgPMqXyrfUPvwUS9XsWpN9YbsivqVuqA5MisnBsfjIV1OZzLmM7r4rEhU cQxiyVT/nJT1+ezRowa32EHiGcj36++XsPQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudekuddgheeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeffmhhi thhrhicuifhuthhovhcuoegumhhithhrhiesghhuthhovhdruggvvheqnecuggftrfgrth htvghrnhepiefgteevheevveffheeltdeukeeiieekueefgedugfefgefhudelgfefveel vdevnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepug hmihhtrhihsehguhhtohhvrdguvghv X-ME-Proxy: Feedback-ID: i0e71465a:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 19 Sep 2023 11:15:52 -0400 (EDT) Content-Language: en-US In-Reply-To: <83fs3ackrq.fsf@gnu.org> Received-SPF: pass client-ip=66.111.4.25; envelope-from=dmitry@gutov.dev; helo=out1-smtp.messagingengine.com X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-1.473, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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:310778 Archived-At: On 19/09/2023 17:14, Eli Zaretskii wrote: >> This is very simple - I suggest to not touch xdisp.c as much as >> possible, just make sure that it is interlocked. And focus on async >> support in Elisp code. Once there is async support in Elisp code, we can >> move further and look into xdisp. >> >> (I suggest this because I feel that xdisp is a rabbit hole we may sink >> in instead of doing something more productive) > I'm actually of the opposite opinion. I think trying to parallelize > redisplay is a lower-hanging fruit, and if successful, it could bring > non-trivial gains to Emacs even if the rest remains single-threaded. Do we have evidence that the speed of redisplay is a limiting factor in general Emacs usage? I.e. with an optimized build and most of the popular modes (excepting certain display-heavy Org buffers, let's say).