- **Patch**: push --> waiting
- **Type**: Enhancement --> Maintainability
- **Comment**:

Depends on issue 5373 and will get pushed along with it.



---

** [issues:#5874] Remove all uses of markup macro from scm/*.scm**

**Status:** Started
**Created:** Mon Mar 30, 2020 08:14 PM UTC by David Kastrup
**Last Updated:** Sun Apr 05, 2020 06:39 AM UTC
**Owner:** David Kastrup


Remove all uses of markup macro from scm/*.scm

The markup macro is a major portability headache for getting
byte-compilation with Guilev2 to work.  This removes all uses of it
from within the scm code base of LilyPond while keeping it around (for
now) for use from files in LilyPond syntax.


This actually also includes the single commit from

Issue 5873: Refactor \markup \pattern

http://codereview.appspot.com/575930043


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development

Reply via email to