Okay, so it's not just me hitting that thing. There's a missing dependency in 
the Documentation build that's probably uncovered by recent performance 
improvements in LilyPond. I don't think it's this patch. If you didn't prune 
your tree yet, you may just retry running 'make doc' and hope that 
internals.texi is processed first. I'll submit a proper fix tomorrow.


---

** [issues:#5923] Use a hash table for the lexer keywords**

**Status:** Started
**Created:** Mon Apr 20, 2020 08:10 AM UTC by Han-Wen Nienhuys
**Last Updated:** Mon Apr 20, 2020 08:32 PM UTC
**Owner:** Han-Wen Nienhuys


Get rid of unused function ly:lexer-keywords.

https://codereview.appspot.com/549920043


---

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

Reply via email to