[Top][All Lists]

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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5437 Improve

From: Auto mailings of changes to Lily Issues via Testlilyissues-auto
Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5437 Improve markup->string
Date: Mon, 12 Nov 2018 21:02:03 -0000

As stated on Rietveld, with
a glitch was introduced.
While I'm pretty sure the current patch-set cures it, I'm simply not sure whether other bad stuff is introduced - there are so many markup-(list-)commands...
This convinces me, we do need a regtest for markup->string.

So I stop the review for now (setting this to needs-work) and start thinking how such a regtest could be done.

Suggestions are highly appreciated.

[issues:#5437] Improve markup->string

Status: Started
Created: Sat Nov 10, 2018 12:48 PM UTC by Thomas Morley
Last Updated: Mon Nov 12, 2018 01:12 PM UTC
Owner: Thomas Morley

Improve markup->string

'all-relevant-markup-commands' is now a toplevel-defined procedure.
So it is not longer a part of the rekursive 'markup->string'.
It needs to be a procedure, because not all bindings of the
lily-module are already done in markup.scm, so it should be
evaluated at the time 'markup->string' is called.
Additionally we gain the chance to have user-defined
markup-commands from '(current-module)' been processed as well.

Sent from because address@hidden is subscribed to

To unsubscribe from further messages, a project admin can change settings at Or, if this is a mailing list, you can unsubscribe from the mailing list.

Testlilyissues-auto mailing list

reply via email to

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