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: Variable pitch text filling Date: Wed, 01 Dec 2021 18:42:26 +0200 Message-ID: <83bl20s2dp.fsf@gnu.org> References: <87ilwft1ph.fsf@gnus.org> <875ysft0l3.fsf@gnus.org> <835yse3n01.fsf@gnu.org> <87lf1ars0f.fsf@gnus.org> <83czmm11t0.fsf@gnu.org> <87h7byrplm.fsf@gnus.org> <83a6hq0zey.fsf@gnu.org> <87lf19r7uv.fsf@gnus.org> <83tufxy7f0.fsf@gnu.org> <83o865xuf3.fsf@gnu.org> <87v90b136m.fsf@gnus.org> <83tufvukjj.fsf@gnu.org> <875ysbxal0.fsf@gnus.org> <83h7bvugxm.fsf@gnu.org> <87sfvessx6.fsf@gnus.org> <87wnkp9c3t.fsf@gnus.org> <87ee6wanra.fsf@gnus.org> <83r1awse4k.fsf@gnu.org> <87sfvc8kdw.fsf@gnus.org> <83czmgs7t1.fsf@gnu.org> <87k0go8ios.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15671"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 01 17:53:55 2021 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 1msSri-0003sE-1G for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Dec 2021 17:53:54 +0100 Original-Received: from localhost ([::1]:53808 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1msSrg-00088d-OL for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Dec 2021 11:53:52 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:42058) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1msSgt-0002jA-TU for emacs-devel@gnu.org; Wed, 01 Dec 2021 11:42:43 -0500 Original-Received: from [2001:470:142:3::e] (port=57038 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1msSgs-0002r3-1Z; Wed, 01 Dec 2021 11:42:42 -0500 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=ICgtzOC850V+IxRncqAId91B4ejnFvL6wBKRCteSIyo=; b=Px+9Tyn5y/yQ aizQzsnkxQLyVY9xjmrRJm5Uj0P8dfkxMotMnrDksCVAH+5MYhrcdsLzA66razn7kK7mMPzfUE32h Ri1CTbe9QUEm4iiewuOi2eoPFPNPgFEQLZIywrTUmx5fQp2ElvxY9jWyg2JpI4uIZFi53XVM6gbLH B4bkV39tLrQtACJRlSqB8Da4C4KAtDdc7p855YlQwANkkOxQVsY+k6IGxySArmZfkWHmDJMPtuO7S ueVzv6WzVu06NVpWE454PscZFsemnuZNvJ0mZy0uShKSJvfiXEMtVKPacpI/688LPliJRM1yXffxa y0MfSTGem0wcjbcV3fbPSA==; Original-Received: from [87.69.77.57] (port=3536 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1msSgr-0000Uu-Ox; Wed, 01 Dec 2021 11:42:42 -0500 In-Reply-To: <87k0go8ios.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 01 Dec 2021 16:10:27 +0100) 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" Xref: news.gmane.io gmane.emacs.devel:280643 Archived-At: > From: Lars Ingebrigtsen > Cc: emacs-devel@gnu.org > Date: Wed, 01 Dec 2021 16:10:27 +0100 > > Eli Zaretskii writes: > > > In what way is min-width inefficient? > > I'm not sure -- you're the one who said it was? But it does to a lot of > work, dropping into the start/stop machinery and doing computations. > This new property is purely on a char by char basis, so it doesn't have > to do any of that stuff. OK, I will have a look. I don't think what we have is expensive, but maybe I'm missing something. > > I'm not sure I understand the "recursive" part: if some string has a > > certain value of some text property, then every character of that > > string has that same value of that property, and thus you cannot have > > some of those characters have the same property with a different > > value. So how can the "recursive" part work in practice? > > You'd have to maintain a stack in the `min-width' machinery to handle > "overlapping" (or rather, nesting) min-width display properties. I'd > rather not. So what are the requirements for the replacement feature here?