A repository of reusable LilyPond code snippets, functions, engravers, and templates, designed for direct inclusion in music scores.
openLilyLib/snippets is a repository of reusable LilyPond code snippets, including custom functions, engravers, templates, and examples. It provides an organized, version-controlled collection of code that LilyPond users can directly include in their music scores, eliminating the need to manually copy and paste snippets from other sources.
LilyPond users, music engravers, and composers who want to leverage pre-built, reusable code for tasks like editorial tools, custom notation, or template-based score creation.
It offers a collaborative, modern alternative to the LilyPond Snippet Repository (LSR) with version control, direct includability, and compatibility across LilyPond versions, making snippet management and reuse more efficient.
A place to store useful pieces of LilyPond code - custom functions, engravers, hacks, templates, examples etc.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Snippets are provided as .ily files that can be directly included in LilyPond documents via \include, eliminating the need for manual copy-pasting from sources like the LSR.
Hosted on GitHub, it enables community contributions and change tracking, offering a modern alternative to the static LilyPond Snippet Repository.
Snippets are not tied to a single LilyPond engine, ensuring they work across releases and reducing version lock-in.
Most snippets include compilable .ly example files, providing practical demonstrations of usage and reducing trial-and-error.
Contains unsorted directories like 'fried-library-to-be-sorted' and deprecated scripts, indicating incomplete curation and potential usability issues.
Requires manual installation and configuration of LilyPond's include path, which can be cumbersome and error-prone for new users.
Lacks a table of contents or proper documentation system, forcing users to browse directories to find snippets, as admitted in the README.