- **Patch**: new --> needs_work
- **Comment**:

Now it just sits at 

~~~
...
Making Documentation/out/contributor.texi (copy)
Making Documentation/out/web.texi (copy)
Making Documentation/out/changes.texi < tely
Making Documentation/out/internals.texi 
Making Documentation/out/essay.texi < tely
Making Documentation/out/music-glossary.texi < tely
Making Documentation/out/learning.texi < tely
langdefs.py: warning: lilypond-doc gettext domain not found.
Making Documentation/out/usage.texi < tely
langdefs.py: warning: lilypond-doc gettext domain not found.
Making Documentation/out/extending.texi < tely
langdefs.py: warning: lilypond-doc gettext domain not found.
Making Documentation/out/snippets.texi < tely
langdefs.py: warning: lilypond-doc gettext domain not found.
langdefs.py: warning: lilypond-doc gettext domain not found.
langdefs.py: warning: lilypond-doc gettext domain not found.
langdefs.py: warning: lilypond-doc gettext domain not found.


~~~

when running 'make'



---

** [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:** Tue Apr 21, 2020 01:33 PM UTC
**Owner:** Han-Wen Nienhuys


Get rid of unused function ly:lexer-keywords.

https://codereview.appspot.com/549920043


---

Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net 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
testlilyissues-a...@lists.sourceforge.net
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
    • ... 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
    • ... 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