From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs design and architecture. How about copy-on-write? Date: Tue, 19 Sep 2023 18:37:38 +0300 Message-ID: <838r92cgxp.fsf@gnu.org> 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> <99e84ae7-b3aa-a009-5cb8-a75826343196@gutov.dev> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4685"; mail-complaints-to="usenet@ciao.gmane.io" Cc: yantar92@posteo.net, acm@muc.de, incal@dataswamp.org, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Sep 19 17:38:59 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 1qicoV-00011M-C7 for ged-emacs-devel@m.gmane-mx.org; Tue, 19 Sep 2023 17:38:59 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qicnd-0001B4-QP; Tue, 19 Sep 2023 11:38:05 -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 1qicnb-0001Aj-5O for emacs-devel@gnu.org; Tue, 19 Sep 2023 11:38:03 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qicnW-0001Lb-UB; Tue, 19 Sep 2023 11:37:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=lXoKE70h1JxNasAjGgfF+e7Lk36kdryO/iNHkze2U1w=; b=J3ltRnxkx6Ud y/KH7pR3zG2RLRc1jNDNxTTRFx95kCdz+Qx2KXbteU8SKr9QMvZcP4LrYNBDFZ8cb+I25q9W6wq1N /MPlOOwt7M4vRZGE4llA8aNxAaBH1/d9wbIKkoEOM6nzMWOkQ37dKwPCt0DvNpNAEc9MSSUTguqE8 gptICm3vmWS5tHX1Ctp6Zf8S51MBsjs1UBRTq0+qF2dzqmxOXuqfKAATGA36Ivrt3BCAHK8IBuj/k LXdeOaB6BZUR4kecya3Um0DBiUhGBrtsCiS3oJIMgMt/SdpDgDVy60Fy3VbN3fUrO2n5LCQkbF0bA lmEysvZdv5P6dLh/FfNxfg==; In-Reply-To: <99e84ae7-b3aa-a009-5cb8-a75826343196@gutov.dev> (message from Dmitry Gutov on Tue, 19 Sep 2023 18:15:50 +0300) 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:310779 Archived-At: > Date: Tue, 19 Sep 2023 18:15:50 +0300 > Cc: acm@muc.de, incal@dataswamp.org, emacs-devel@gnu.org > From: Dmitry Gutov > > 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). You already forgot the long-lines problems? And there are other situations where we'd like faster redisplay, even though they are not as bad. For example, when a session has many frames (I believe Stefan Monnier tends to have a lot of them in his sessions). To say nothing of the fact that displays become larger and larger, and many people like to have their frames maximized.