Re: Variable pitch text filling

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 01 Dec 2021 16:10:27 +0100
> 
> Eli Zaretskii <eliz@gnu.org> 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?