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: Thu, 21 Sep 2023 16:00:29 +0300 Message-ID: <837cojadg2.fsf@gnu.org> References: <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> <838r92cgxp.fsf@gnu.org> <837comcam8.fsf@gnu.org> <6946e6f0-c6ef-186c-35d4-c09935c05a07@gutov.dev> <83y1h1axtq.fsf@gnu.org> <87sf79rq5o.fsf@yahoo.com> <83fs38c2yv.fsf@gnu.org> <83o7hw9ee1.fsf@gnu.org> <87il84q845.fsf@yahoo.com> <83il849bx6.fsf@gnu.org> <87a5tfri8c.fsf@yahoo.com> <878r8z27cs.fsf@localhost> <44e98df7-f683-ac07-e644-40757f1d26f9@gutov.dev> <87msxfzts6.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4182"; mail-complaints-to="usenet@ciao.gmane.io" Cc: dmitry@gutov.dev, luangruo@yahoo.com, acm@muc.de, incal@dataswamp.org, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Sep 21 15:05:13 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 1qjJMn-0000ml-3L for ged-emacs-devel@m.gmane-mx.org; Thu, 21 Sep 2023 15:05:13 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qjJM3-0000iI-A3; Thu, 21 Sep 2023 09:04:27 -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 1qjJIO-0001la-RT for emacs-devel@gnu.org; Thu, 21 Sep 2023 09:00:44 -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 1qjJIK-0002t0-S0; Thu, 21 Sep 2023 09:00:38 -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=kpiiWvOj4mDhOdfMfOFmMEDrBEcvncZ8JUBXn7iRXEw=; b=Mukcv+b0ZwFY mKaFsPBojp2ILoG+VLF1oeP0K0w18Ay7Llv1IZ4wW2eMyEwknCPcGhb7/COxmpDUVQRws/rsFdjZf qvqmPeoW03z744rTgUGmGPbcApUaLl7v9tJk/24nqfjsk3Bb5sMEFs6nbAc7RacyvcmDF2S4Q9rBJ 62+XglAJrrfrTwJeCKviQQsz/QGegY1h0cLaYg25sfDyfkK7BJzX8TC1k7a5k8pRiY7p7QfrRoy9G 57sVgUNTA2bsDCLfOFRkpTRSCqRGSLczputRztdR2khcBguiDpyv9UiMq4zd+6hqPte2tgLUfY2hI 04mSX7j9dSnl/1Ezse5FFQ==; In-Reply-To: <87msxfzts6.fsf@localhost> (message from Ihor Radchenko on Thu, 21 Sep 2023 10:48:25 +0000) 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:310894 Archived-At: > From: Ihor Radchenko > Cc: Po Lu , Eli Zaretskii , acm@muc.de, > incal@dataswamp.org, emacs-devel@gnu.org > Date: Thu, 21 Sep 2023 10:48:25 +0000 > > Dmitry Gutov writes: > > >> I think that there is at least one way to address long lines using > >> asynchronous redisplay - put a placeholder on the problematic line and > >> continue calculating the actual rendering in the background instead. > >> That will not force us to compromise between rendering time and > >> accuracy, as we do now, with long-line-threshold. > > > > Until you're laid out the long line, you don't know which screen line it > > will finish at, or at which height specifically (it might have images, > > or taller text due to faces, etc). So you can't render the remainder of > > the buffer either. > > What I had in mind is the processing to happen in two stages: (1) > calculate "quick-and-dirty" layout; (2) start calculating "accurate" > layout. If calculating "accurate" layout takes long time, go ahead and > draw the "quick-and-dirty" version on the glass, while "accurate" > version continues being computed in the background. > > Of course, this threshold should be configurable. > > >> Similar approach might be used to render mode lines - render a > >> placeholder until it is fully calculated, keeping Emacs responsive. > > > > I hope by "placeholder" you mean the previous rendered image of it. > > More precisely, what I had in mind is the old glyph matrix + some > indication that the rendering is not up-to-date (like classic sand clock > icon) You are basically proposing us to provide broken, incorrect, and outdated display in some cases. That won't fly, so it's a non-starter.