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 16:45:14 +0200 Message-ID: <83czmgs7t1.fsf@gnu.org> References: <87ilwft1ph.fsf@gnus.org> <837dcv2c2c.fsf@gnu.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> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27186"; 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 15:52:56 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 1msQyc-0006oW-I8 for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Dec 2021 15:52:54 +0100 Original-Received: from localhost ([::1]:58248 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1msQya-0004Fh-LM for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Dec 2021 09:52:52 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:53582) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1msQrS-00066M-6C for emacs-devel@gnu.org; Wed, 01 Dec 2021 09:45:30 -0500 Original-Received: from [2001:470:142:3::e] (port=51410 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 1msQrR-0002yB-S7; Wed, 01 Dec 2021 09:45:29 -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=6DZzPjFuoyjRViRPOQJBXSW06i+YyzCaXm389eXnKFw=; b=dOEwz4CwPUNQ xS8vksI07GRRyNJJLy6kYe8qg6az7TNGjBEJEwlTmsHJIilGMTZ4JxPr85k+27IkMFEW+iC5UlS8h VO3Ji2LQRnBrevyqa4irgR3rzoAiy51c0zIHLK3CBmks7t1NYhnlYyyaSDO01Wz/0/NqbXHhZqSPe F7j07e/B92dd9izfl6FPgExksmnwKTe1T1lp8lG1n3l3IE03p2+4Dppp6aW6pJfM+2pTGHB+KTSM2 OS+mihI7UqJ35VkJcsiHHNfzyP9r2F9cj3tlhqb3x6K8iJRHlFjPtvyRdte66Wk3CHOKCIgkCOhPb Z8oU3KqfmkWPmNdEW6fZQA==; Original-Received: from [87.69.77.57] (port=4300 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 1msQrR-0002A6-OM; Wed, 01 Dec 2021 09:45:29 -0500 In-Reply-To: <87sfvc8kdw.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 01 Dec 2021 15:33:47 +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:280631 Archived-At: > From: Lars Ingebrigtsen > Cc: emacs-devel@gnu.org > Date: Wed, 01 Dec 2021 15:33:47 +0100 > > > We already have 1), it just needs some loving care, AFAIU? What is > > missing in min-width to provide 1) ? > > For min-width provides both 1) and 2), but it's inefficient for both, so > I think it makes sense to allow both these things in the char-spacing > (or whatever we're calling it) thing. > > As a practical matter, `min-width' doesn't support nesting now, and we'd > have to make it recursive to allow having both a `min-width' on a series > of characters and on separate characters (as we need in the U:--- thing > in the mode line), which would further make `min-width' more inefficient. In what way is min-width inefficient? 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?