From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Emacs design and architecture. How about copy-on-write? Date: Thu, 21 Sep 2023 10:48:25 +0000 Message-ID: <87msxfzts6.fsf@localhost> 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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34857"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Po Lu , Eli Zaretskii , 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 Thu Sep 21 14:48:11 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 1qjJ6J-0008uZ-75 for ged-emacs-devel@m.gmane-mx.org; Thu, 21 Sep 2023 14:48:11 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qjJ16-0007dv-R5; Thu, 21 Sep 2023 08:42:48 -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 1qjJ08-0006Bt-RH for emacs-devel@gnu.org; Thu, 21 Sep 2023 08:41:49 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qjIze-0001nT-JJ for emacs-devel@gnu.org; Thu, 21 Sep 2023 08:41:45 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 5D650240101 for ; Thu, 21 Sep 2023 12:47:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1695293229; bh=Gi6z1z2rJC0KZXqP1yuwszvsU+InA/eqlLgAParzoco=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=G2vCSiqUg3ofR5C3kEniSlEtxAGnwnRdaEPxfvLbfwOoEJwk0ilZoMg/j7S56EQAi VwEU0BiNYJvvMcazmB97hnGAQCRP1qDIAS07x45vOQUAMYbUY9rlPTFpU6JtKWT2V8 TMTSM9lY2EOIYEt0NPL1GyAD+JZfBErq7/YACttsTpxPXX5J6/wx7t2eOGLN2JtCvW V3snjLaEQ3eRHo4UVav+yo0GDUdS/ruCy11o6Pa4NskD2BxpcPwMdM1MfhFrVSIND8 i9bUW8qSsrNmhuFb6eBMaXabdYPxQSchYthAqjmaTBd7nZOMA3AgolM+gfVE6RGZMP 4Z1x/EePdg/ng== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4RrsXr5Rn7z6tw6; Thu, 21 Sep 2023 12:47:08 +0200 (CEST) In-Reply-To: <44e98df7-f683-ac07-e644-40757f1d26f9@gutov.dev> Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 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:310888 Archived-At: 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) > ... But then the mode-line won't be refreshed at 60fps still, which > some said is a good goal? (I tentatively agree). I also agree that it is a good goal. The scenario I had in mind is poorly written third-party mode line packages that, for example, query git on every redisplay. There is nothing we can do about poor Elisp code in third-party packages, but the proposed approach will at least prevent Emacs being laggy or hanging in the eyes of the user. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at