Hi Richard, I was curious about how AI can help with this question. So I asked Claude (Opus 4.7 Adaptive) with the following prompt ``` LilyPond question: Is there a list of event types somewhere in the docs? Ground your answers with real references in lilypond docs ``` And here is its response ``` 1. Named events (the FooEvent objects)
The canonical list lives in the *Internals Reference* under what is called "Music expressions" in current docs (it was called "Music classes" in older versions). Every named event — NoteEvent, ArticulationEvent, CrescendoEvent, BreathingEvent, etc. — has its own page there. - Stable 2.24: https://lilypond.org/doc/v2.24/Documentation/internals/music-expression <https://lilypond.org/doc/v2.24/Documentation/internals/music-expressions> - The Extending manual points you there explicitly: "All classes of music are listed in the Internals Reference, under Music classes... A list of all expressions available is in the Internals Reference manual, under Music expressions." 2. Event classes (the type-tag hierarchy) These are the symbolic tags (note-event, rhythmic-event, dynamic-event, slur-event…) that engravers and \listen/dispatchers key off. The most useful single page is the *music-event* entry in the Internals Reference, which enumerates every music object that is a music-event: - https://lilypond.org/doc/v2.24/Documentation/internals/music_002devent It lists AbsoluteDynamicEvent, AdHocJumpEvent, AdHocMarkEvent, AlternativeEvent, AnnotateOutputEvent, ApplyOutputEvent, ArpeggioEvent, ArticulationEvent, BarEvent, BassFigureEvent, BeamEvent, BeamForbidEvent, BendAfterEvent, BendSpanEvent, BreakDynamicSpanEvent, BreathingEvent, CaesuraEvent, ClusterNoteEvent, CodaMarkEvent... and so on — essentially every event in the system. ``` The text script event is found on this page: https://lilypond.org/doc/v2.24/Documentation/internals/music_002devent Hope it helps On Wed, May 20, 2026 at 3:19 PM Richard Shann <[email protected]> wrote: > I couldn't find one - I knew of dynamic-event, beam-event ... but > couldn't think of the name for markup (text-script-event) and when I > asked Al he said it was markup-event, which just goes to show what Al > knows :) > Richard > > >
