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: Fri, 22 Sep 2023 10:28:23 +0000 Message-ID: <87ediqy01k.fsf@localhost> References: <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> <837cojadg2.fsf@gnu.org> <33e6ecd3-8f1c-fa02-b5fc-bb39c87b53d7@gutov.dev> <83v8c38wtz.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14670"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Dmitry Gutov , luangruo@yahoo.com, acm@muc.de, incal@dataswamp.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 22 12:27:41 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 1qjdNt-0003eX-5y for ged-emacs-devel@m.gmane-mx.org; Fri, 22 Sep 2023 12:27:41 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qjdNS-0004y1-5D; Fri, 22 Sep 2023 06:27:14 -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 1qjdNQ-0004xt-P5 for emacs-devel@gnu.org; Fri, 22 Sep 2023 06:27:12 -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 1qjdNO-0007Bp-PU for emacs-devel@gnu.org; Fri, 22 Sep 2023 06:27:12 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 60291240105 for ; Fri, 22 Sep 2023 12:27:08 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1695378428; bh=yVXu8ODhPHhYvg+heypp15L8UVI01AW++3ZMNLlpJUE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=QXETjGZl3BaXq+iAs9T4HVcLjpklcqo2FhYtr/2LynU2nUQ4LEtza6U7myWaupiLl CYvCtS1x5nIoLsnyZQ1U71X682GvMDNt/I3Pp9IIWiP++lhYS+cgtGS2M4GH5RfeUL aMCOpGwA1u5XRlbyDRjLb6gtc6PbIUf/egKFSLfBITE2/+FYWwbyDrl/mputUYgoeS 1AABiDahdKr5QtcJ2WELB9EX9vXg7FuKi8G5D1pOdBJvKN/Dmm82KL5vs1m0Nj78Rz ontkqrhGxi7/4CEsNgrtAdAPDwtS7L6GRaylWB2YQjzvyXfqmgcPfgz6uPtLkt7MkD Ff1DbvcZyekPQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4RsT3H2V2Tz6txQ; Fri, 22 Sep 2023 12:27:07 +0200 (CEST) In-Reply-To: <83v8c38wtz.fsf@gnu.org> 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:310947 Archived-At: Eli Zaretskii writes: >> If might prove an okay experience, if the "outdated" part is within >> certain bounds. Like if the current buffer refreshes at 30/60fps, and >> the mode-line at 10/20fps, for example. > > That's not what was proposed. The proposal was to do a > "quick-and-dirty" layout first, and use the results if the "accurate" > layout takes too long. The quick-and-dirty layout can only be based > on ignoring changes in fonts and disregarding images and stuff like > that, so the screen lines will be wrong, and you will see them jump > and/or rearrange after some delay, which could be some seconds. Some > browsers do that when they need to download images, and it always jars > me when that happens. Usually, I also lose the place where I was > reading. > > I hope Emacs will never behave like that. I can see how this can be annoying. What about "quick-and-dirty" layout being "empty" window that is also blocked for user interaction. (I am assuming that redisplay is asynchronous here). Then, the user will be blocked from interacting with a single problematic window being redisplayed, but could still work with other windows/buffers without waiting for Emacs to "unhang". -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at