[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: markup->string

From: Jean Abou Samra
Subject: Re: markup->string
Date: Tue, 15 Nov 2022 14:49:55 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1

Le 15/11/2022 à 14:43, David Kastrup a écrit :
If it's "mundane", why would the conversion result in a complex

Have you looked at the replacement?

It is

(lambda* (m #:optional headers)
  (if headers
      (markup->string m #:props (headers-property-alist-chain headers))
      (markup->string m))

which is the only thing convert-ly can programmatically
replace markup->string with to make the change equivalent to

(markup->string x) -> (markup->string x)     [no change]
(markup->string x headers) -> (markup->string x #:props 
(headers-property-alist-chain headers))

The "complexity" we are talking about is the length of the output
of convert-ly relative to the input. There is no complex logic
at all.

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]