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: Debouncing slow mode line constructs (was: Emacs design and architecture. How about copy-on-write?) Date: Fri, 22 Sep 2023 10:23:47 +0000 Message-ID: <87h6nmy098.fsf@localhost> References: <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> <7b0c07f5-88c8-4f2c-6ac6-a6112c884f32@gutov.dev> <87il83zsg1.fsf@localhost> <87fs37zrjx.fsf@localhost> <83ttrn8woc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32519"; 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: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 22 12:23:33 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 1qjdJs-0008GX-MJ for ged-emacs-devel@m.gmane-mx.org; Fri, 22 Sep 2023 12:23:32 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qjdJ3-0002fE-Nn; Fri, 22 Sep 2023 06:22:41 -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 1qjdJ2-0002eM-D1 for emacs-devel@gnu.org; Fri, 22 Sep 2023 06:22:40 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qjdIx-0006BT-DM for emacs-devel@gnu.org; Fri, 22 Sep 2023 06:22:40 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id C9EBE240029 for ; Fri, 22 Sep 2023 12:22:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1695378152; bh=fHlS7PdPFaLmgCNFEbt5QkIkYciiQjzfQYvYUGIHViE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version: Content-Transfer-Encoding:From; b=XHA00rvxqvPgAmQlSXle1I558BtTtPbt3jb/8+1u49mRANn3qH3uJFi7YAg4XzVDK 2+GCrlNOs3yprR13B+7sckmE26c63eoJOFj87m4BqWiecJY82uQ//nOIbctZBsBsLc CReII81pvOW3bCsLCDBzclEu4uesK2fUhRkJzSoeg9VDOyn4f4X5d1KdITkqSXnILC PadPLBmmz/t3QeNLh/9OpuuL/d3gdPeyjyMY0hubN0M7bAZQY1EL2R4cRzScHiAXzS MvCEDRB/K/q2M5jvC8y8fVNtKjYwqOw4UIxwiMh98mNhFIrqGysv1vVI549WyTGNn7 V5ifnCaC6QJZg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4RsSxz5y81z9rxK; Fri, 22 Sep 2023 12:22:31 +0200 (CEST) In-Reply-To: <83ttrn8woc.fsf@gnu.org> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.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=unavailable 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:310946 Archived-At: Eli Zaretskii writes: >> What about automatically debouncing slow :eval constructs in the mode >> line? If we make sure that :eval constructs running longer than a >> threshold do not run too frequently, it can certainly improve user >> experience. > > How do you propose to evaluate just portions of the mode line? What > will the :eval whose processing is bypassed yield, and how will that > affect processing of the rest of mode-line-format, given its > highly-recursive processing structure and the fact that the text > produced by this processing is laid out as it is produced? What I have in mind is the following: 1. Every time Emacs processes :eval construct it (a) measures the time taken; (b) caches return value. The total mode line render time is also recorded. 2. If the total render time exceeds configurable threshold, processing the most time-consuming :eval constructs will be suspended until "debounce" time since the last full processing. By "suspended", I mean that cached :eval value is reused instead of invoking :eval again. Possibly, not reused verbatim, but by replacing the cached value with some kind of placeholder that has the same total height/width as the cached value. For example, consider :eval segment invoking external git command and producing branch name: "=E2=9B=AC master". If that command takes too long, Emacs will display "=E2=8F=B3 " instead of "=E2=9B=AC master", until the mode-line redisplay that is some fixed time ahead. 3. After "debounce" time since the last "suspend", all the :eval are processed in full again, generating up-to-date mode-line. In terms of values, I am thinking something like 0.2 sec for threshold and 1.0 sec for debounce. This way, mode line will be outdated no longer than 1 second. --=20 Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at