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: Debouncing slow mode line constructs (was: Emacs design and architecture. How about copy-on-write?) Date: Fri, 22 Sep 2023 16:14:16 +0300 Message-ID: <83v8c25p07.fsf@gnu.org> References: <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> <400f8781-6bd9-53a0-0ace-26c327890fd9@gutov.dev> <87msxey105.fsf@localhost> <83lecy777w.fsf@gnu.org> <87ttrmwetx.fsf@localhost> <831qeq741p.fsf@gnu.org> <87il82wdyn.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40058"; 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 Fri Sep 22 15:14:28 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 1qjfzI-000AEZ-I6 for ged-emacs-devel@m.gmane-mx.org; Fri, 22 Sep 2023 15:14:28 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qjfz7-0005Fd-H8; Fri, 22 Sep 2023 09:14:18 -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 1qjfyz-0005BD-CH for emacs-devel@gnu.org; Fri, 22 Sep 2023 09:14:10 -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 1qjfyy-00047K-84; Fri, 22 Sep 2023 09:14:08 -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=31KO4GCnwHxb4acMF50wqwBHbvdYQoKzweH97hUjesE=; b=IOcFZcjGa5hs KTvRBCCk0Uy6ubKIQNFV9wLaxeggDVG7TQcwCK0VuKKxkvPw/Fx0D9e4s7XiK4HL5t8ohy7Hjc0jM TsYPZFSOYq5HRSVD9kcrDGkDaL70wMNS/XOV6R+3J7kPwM8ThIHi7xpg4tV4Xp3+htqHje7TI+/UK c25ZYkjxA31GALRtbk8EJhBNlrYlOMpaKkXimcO5gA0+w/rjZJEax8wgC+QjSpCLFPDxY0x4jMfkn 9lFesS1uK51vjEI6YCLhy+9gJLDdVZxanlsgbtTDxC8Okr+R3cnRWeMZdnH5Bm3yvaX7slzK2TTLb ABc+xg6MhTltmSuCeBd7tA==; In-Reply-To: <87il82wdyn.fsf@localhost> (message from Ihor Radchenko on Fri, 22 Sep 2023 13:10:40 +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:310967 Archived-At: > From: Ihor Radchenko > Cc: dmitry@gutov.dev, luangruo@yahoo.com, acm@muc.de, incal@dataswamp.org, > emacs-devel@gnu.org > Date: Fri, 22 Sep 2023 13:10:40 +0000 > > Eli Zaretskii writes: > > > I don't see a reason to do that with this particular kind of problems. > > We currently don't display anything by default even if Lisp called by > > redisplay signals an error, we just log that in *Messages*. Why > > should these :eval problems we treated differently? > > The aim here is to make users aware that the proposed optimization is > activated. It does not have to be warning specifically. Might be > something else visible enough. Warning was just the first thing that > came to my mind. They can look at *Messages* and see the warning there, like they do with any other redisplay problem.