LilyPond wiki - User contributions [en]

Coloring elements of notation

2026-04-07T11:37:32Z

Jean Abou Samra:

Individual objects may be assigned colors. Several pre-defined colors are available; they are [https://lilypond.org/doc/v2.25/Documentation/notation/list-of-colors.html exhaustively listed] in the Notation Reference.

<lilypond version="2.24">
\relative c'' {
\override NoteHead.color = #red
c4 c
\override NoteHead.color = #(x11-color 'LimeGreen)
d
\override Stem.color = #blue
e
}
</lilypond>

[[Category:Editorial annotations]]
[[Category:Really simple]]
[[Category:Snippet]]

Coloring elements of notation

2026-04-07T11:36:55Z

Jean Abou Samra: Undo revision 6522 by Jean Abou Samra (talk)

Individual objects may be assigned colors. Several pre-defined colors are available; they are exhaustively listed in the Notation Reference.

<lilypond version="2.24">
%% http://lsr.di.unimi.it/LSR/Item?id=419

\relative c'' {
\override NoteHead.color = #red
c4 c
\override NoteHead.color = #(x11-color 'LimeGreen)
d
\override Stem.color = #blue
e
}
</lilypond>

[[Category:Editorial annotations]]
[[Category:Really simple]]
[[Category:Snippet]]

Coloring elements of notation

2026-04-07T11:35:14Z

Jean Abou Samra:

Individual objects may be assigned colors. Several pre-defined colors are available; they are [https://lilypond.org/doc/v2.25/Documentation/notation/list-of-colors.html exhaustively listed] in the Notation Reference.


\version "2.24"

%% <nowiki>http://lsr.di.unimi.it/LSR/Item?id=419</nowiki>

\relative c<nowiki>''</nowiki> {
<nowiki> </nowiki> \override NoteHead.color = #red
<nowiki> </nowiki> c4 c
<nowiki> </nowiki> \override NoteHead.color = #(x11-color 'LimeGreen)
<nowiki> </nowiki> d
<nowiki> </nowiki> \override Stem.color = #blue
<nowiki> </nowiki> e
}


[[Category:Editorial annotations]]
[[Category:Really simple]]
[[Category:Snippet]]

Splitting chords

2026-04-07T09:51:33Z

Jean Abou Samra:

This snippet is a 2009 contribution by Gilles Thibault in [https://lists.gnu.org/archive/html/lilypond-user/2009-01/msg00685.html lilypond-user]. It provides two functions to split a chord sequence into two separate voices, also preserving articulations and slurs: <code>\keepOnlyFirstNote</code> extracts the first note (as given in the input; this is usually the lowest one) of every chord, and <code>\deleteFirstNote</code> collects the remaining notes.

Note that these functions don't support <code>q</code> to repeat the last chord.

<lilypond version="2.24">
#(define (has-duration? music)
(ly:duration? (ly:music-property music 'duration)))

#(define (not-has-duration? music)
(not (has-duration? music)))

keepOnlyFirstNote =
#(define-music-function (music) (ly:music?)
(music-map
(lambda (evt)
(when (eq? 'EventChord (ly:music-property evt 'name))
(let ((elts (ly:music-property evt 'elements)))
(when (has-duration? (car elts))
(ly:music-set-property!
evt 'elements
(cons (car elts)
(filter not-has-duration? (cdr elts)))))))
evt)
music))

deleteFirstNote =
#(define-music-function (music) (ly:music?)
(music-map
(lambda (evt)
(when (eq? 'EventChord (ly:music-property evt 'name))
(let ((elts (ly:music-property evt 'elements)))
(when (has-duration? (car elts))
(ly:music-set-property! evt 'elements (cdr elts)))))
evt)
music))

music = \relative c' {
<c e>4-> <d f>( ) <c e>-. g2 c2
}

\markup { Music with chords }
\new Staff \music

\markup { Music split into two staves }
<<
\new Staff \deleteFirstNote \music
\new Staff \keepOnlyFirstNote \music
>>
</lilypond>

[[category:Chords]]
[[category:Scheme]]
[[category:Really cool]]

Coloring individual staff lines

2026-04-07T09:46:10Z

Jean Abou Samra:

Staff lines can be colored independently by overriding the default stencil for <code>StaffSymbol</code>.

The <code>StaffSymbol</code> callback <code>color-staff-lines</code> takes a set of colors (using LilyPond's predefined colors or the functions <code>x11-color</code> and <code>rgb-color</code>) which are applied to each staff line in turn starting with the fifth line (for a standard staff), or each item in the list for custom staves defined with <code>line-positions</code>. To signal that a particular line between colored lines should remain black, use <code>#f</code>.

Contributed by Neil Puttock.

<lilypond version="2.24">
#(define-public ((color-staff-lines . rest) grob)

(define (index-cell cell dir)
(if (equal? dir RIGHT)
(cdr cell)
(car cell)))

(define (index-set-cell! x dir val)
(case dir
((-1) (set-car! x val))
((1) (set-cdr! x val))))

(let* ((common (ly:grob-system grob))
(span-points '(0 . 0))
(thickness (* (ly:grob-property grob 'thickness 1.0)
(ly:output-def-lookup (ly:grob-layout grob) 'line-thickness)))
(width (ly:grob-property grob 'width))
(line-positions (ly:grob-property grob 'line-positions))
(staff-space (ly:grob-property grob 'staff-space 1))
(line-stencil #f)
(total-lines empty-stencil)
;; use a local copy of colors list, since
;; stencil creation mutates list
(colors rest))

(for-each
(lambda (dir)
(if (and (= dir RIGHT)
(number? width))
(set-cdr! span-points width)
(let* ((bound (ly:spanner-bound grob dir))
(bound-ext (ly:grob-extent bound bound X)))

(index-set-cell! span-points dir
(ly:grob-relative-coordinate bound common X))
(if (and (not (ly:item-break-dir bound))
(not (interval-empty? bound-ext)))
(index-set-cell! span-points dir
(+ (index-cell span-points dir)
(index-cell bound-ext dir))))))
(index-set-cell! span-points dir (- (index-cell span-points dir)
(* dir thickness 0.5))))
(list LEFT RIGHT))

(set! span-points
(coord-translate span-points
(- (ly:grob-relative-coordinate grob common X))))
(set! line-stencil
(make-line-stencil thickness (car span-points) 0 (cdr span-points) 0))

(if (pair? line-positions)
(for-each (lambda (position)
(let ((color (if (pair? colors)
(car colors)
#f)))
(set! total-lines
(ly:stencil-add
total-lines
(ly:stencil-translate-axis
(if (color? color)
(ly:stencil-in-color line-stencil
(first color)
(second color)
(third color))
line-stencil)
(* position staff-space 0.5) Y)))
(and (pair? colors)
(set! colors (cdr colors)))))
line-positions)
(let* ((line-count (ly:grob-property grob 'line-count 5))
(height (* (1- line-count) (/ staff-space 2))))
(do ((i 0 (1+ i)))
((= i line-count))
(let ((color (if (and (pair? colors)
(> (length colors) i))
(list-ref colors i)
#f)))
(set! total-lines (ly:stencil-add
total-lines
(ly:stencil-translate-axis
(if (color? color)
(ly:stencil-in-color line-stencil
(first color)
(second color)
(third color))
line-stencil)
(- height (* i staff-space)) Y)))))))
total-lines))

\relative c' {
% color all lines in a standard five-line staff
\override Staff.StaffSymbol.stencil = #(color-staff-lines red green yellow blue cyan)
c1 \stopStaff
\revert Staff.StaffSymbol.stencil

\startStaff
% color the fifth, third and second lines only
\override Staff.StaffSymbol.stencil = #(color-staff-lines (rgb-color 0 0.3 0.8) #f grey (x11-color 'LightGreen))
c1 \stopStaff
\revert Staff.StaffSymbol.stencil

\startStaff
% color an individual line in a custom staff
\override Staff.StaffSymbol.line-positions = #'(-4 0 4)
\override Staff.StaffSymbol.stencil = #(color-staff-lines #f red)
c1
}
</lilypond>

[[Category:Staff notation]]
[[Category:Version-specific]]
[[Category:Tweaks and overrides]]
[[Category:Snippet]]

Clef change at the beginning of a piece (alternative)

2026-04-07T09:44:26Z

Jean Abou Samra:

When changing the clef at the beginning of the first measure, Lilypond just changes the clef for the staff. This is how to keep the staff clef and add an extra clef after the time signature and before the first note.

<lilypond version="2.24">
\relative c' {
%% Start with a bass clef :
\clef bass
%% Use a hidden grace note:
\once\hideNotes\grace c64
%% Adjust the clef spacing:
\once\override Staff.Clef.X-extent = #'(1 . 2)
%% Put in the treble clef:
\clef treble
c4 c c c | c1
}
</lilypond>

[[Category:Staff notation]]
[[Category:Pitches]]
[[Category:Tweaks and overrides]]
[[Category:Snippet]]

Clef, key and time signature in square brackets

2026-03-28T12:24:43Z

Jean Abou Samra:

For critical editions, objects like clefs, key or time signatures sometimes need to be written in parentheses to indicate they are missing from the autograph. This can be achieved by simply wrapping the <code>bracketify-stencil</code> function around the object's stencil function. By using <code>\once \override</code>, the effect can be applied to just one clef/key/time signature; by using <code>\override</code> it applies to the whole piece.

<lilypond version="2.24">
\layout { ragged-right = ##t }

\relative c'' {
% Use \once \override if you only want the object immediately following
% to be in brackets.
\override Staff.Clef.stencil = #(lambda (grob)
(bracketify-stencil (ly:clef::print grob) Y 0.1 0.2 0.1))
\override Staff.TimeSignature.stencil = #(lambda (grob)
(bracketify-stencil (ly:time-signature::print grob) Y 0.1 0.2 0.1))
\override Staff.KeySignature.stencil = #(lambda (grob)
(bracketify-stencil (ly:key-signature-interface::print grob) Y 0.1 0.2 0.1))
\time 2/4
\key cis \minor
a4 b8 cis \break
\clef "bass"
c,,2
}
</lilypond>

[[Category:Editorial annotations]]
[[Category:Snippet]]

Expect a warning several times

2026-02-28T11:36:08Z

Jean Abou Samra: Scheme style

There are times when your LilyPond source file prints warnings when compiled and you may want to suppress these warnings from the output. LilyPond has a Scheme function for this: <code>ly:expect-warning</code>. However, there are times when the same warning is printed several times and <code>ly:expect-warning</code> will only hide one warning at a time. Typing this function several times in a row is tedious.

The Scheme function below takes a string that will match some part of the warning, just like <code>ly:expect-warning</code>, but it also takes an integer for the number of times the warning is printed.

<pre>
#(define (expect-warning-times n . args)
(for-each (lambda _ (apply ly:expect-warning args))
(iota n)))
</pre>

A usage example:

<code>#(expect-warning-times 4 "omitting tuplet bracket")</code>

The hint from the documentation: [https://lilypond.org/doc/v2.25/Documentation/internals/scheme-functions scheme-functions]

User talk:Jean Abou Samra

2026-02-23T13:14:26Z

Jean Abou Samra: /* Spam users */ Reply

== Test of email notifications ==

This is a test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 02:46, 2 November 2025 (UTC)

:Another test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:04, 2 November 2025 (UTC)
::Third test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:05, 2 November 2025 (UTC)
:::Reply test. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 03:05, 2 November 2025 (UTC)
::::Yet another test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:14, 2 November 2025 (UTC)

== Default stylesheet for the Wiki ==

Jean,

you've recently removed paper indentation settings from [[Rest styles]], arguing that no indentation is the default for this Wiki. However, this snippet is part of the “official” documentation that doesn't set the indentation to zero by default...

I thus wonder whether it makes sense to synchronize the Wiki with the LilyPond documentation by not providing a default value for the indentation. Another reason to stay with LilyPond's default is that a novice user who tries to compile a snippet might be surprised that it looks differently. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 16:51, 23 November 2025 (UTC)

:I'm surprised. [https://lilypond.org/doc/v2.25/Documentation/contributor/lilypond-formatting This page of the contributor's guide] implies <code>indent = 0</code> is the default in doc snippets. Is it out of date? What are the exact settings used to compile snippets in the docs? It's been too long since I had any idea how the doc build works, I can't find this in the repo right now… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:13, 23 November 2025 (UTC)
::I took the style settings used on the wiki [https://lilypond.org/doc/v2.25/Documentation/usage/other-programs right from the usage manual] in the section that says "you have to effectively mimick how lilypond-book runs lilypond"… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:15, 23 November 2025 (UTC)
:::D'oh. You are correct. My mistake, my memory failed me, and of course I didn't check before writing :-)
:::Sorry for the noise -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:22, 23 November 2025 (UTC)

== cropped SVG images ==

Jean, please have a look at the image in [[Custodes]] – the mensural custodes in the fourth staff are cropped. If you download the SVG image and use a program like `inkview` you can see that the image actually contains the complete glyphs, however, the bounding box is too tight (an old LilyPond issue, as you certainly know).

Is there a possibility to increase the bounding boxes of all images (both horizontally and vertically) using a post-processing step so that cropping can be avoided? -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 10:40, 25 November 2025 (UTC)

:Seems a bit overkill to me. I've added a simple workaround to that snippet. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 12:41, 25 November 2025 (UTC)
::Nice, thanks! I didn't think of this simple fix. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:27, 25 November 2025 (UTC)

== Some CSS code for <nowiki><samp></nowiki> ==

Jean, what do you think of adding something like the following

<pre>
body { quotes: '‘' '’'; }
samp:before { content: open-quote; }
samp:after { content: close-quote; }
</pre>

to the Wiki CSS for the sake of better conversion to Texinfo? My reasoning is as follows.

There is a strong visual difference between <code><nowiki><code></nowiki></code> in the Wiki and <code>@code</code> in Texinfo output: the former produces typewriter text in a box, the latter uses just typewriter. This is fine with the fonts used for Texinfo output except for marking single letters: in Texinfo it is better to use <code>@samp</code> for this situation, producing typewriter text in quotes.

On the Wiki side I would thus like to use <code><nowiki><samp></nowiki></code>, which <code>makelsr.pl</code> converts to <code>@samp</code>. However, it currently produces plain typewriter in the Wiki, which isn't ideal since the contrast to plain text isn't large enough IMHO.

Example: The letter <samp>s</samp> is marked with <code><nowiki><samp></nowiki></code>. My suggestion: The letter ‘<samp>s</samp>’ is marked with <code><nowiki><samp></nowiki></code>.

An alternative would be to give <code><nowiki><samp></nowiki></code> the same appearance as <code><nowiki><code></nowiki></code>. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:15, 30 November 2025 (UTC)

:Done. Thanks for providing the CSS code. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 15:28, 6 December 2025 (UTC)

:: Ah, I missed that with this CSS code the quote characters are also in typewriter, which is not correct. So please add <code>font-family: sans-serif;</code> to both the <code>samp:before</code> and <code>samp:after</code> block.
:: [I haven't found out how to display the quotes with the same font selected by the user to display the main font in Wiki – or is this fixed to always be sans-serif?]

::: Done. I don't know a better solution either. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 14:30, 8 December 2025 (UTC)
:::Thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:48, 9 December 2025 (UTC)

== Search issues ==

Jean,

To get nice snippet headings in the documentation, we often use non-letter stuff like opening and closing quotes in Wiki page titles. However, as I've found out recently, this severely hampers searching. For example, the snippet [[Using \arpeggioBracket to make divisi more visible]] cannot be immediately found by entering “Using arpeggioBracket” (i.e., without the backslash) into the search field.

I now wonder whether the Wiki can be configured to ignore quote characters and the like in the search. If this is not possible, I have to add redirections for all articles with such characters in its name. It's not a big deal since it can be done programmatically, however, not needing this would be a better solution. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:55, 9 December 2025 (UTC)

:AFAIU the autocompletion just matches by title prefix (to be clear, this is not about the search results page you get if you press Enter, which is much more complete). I think it's not too bad, not sure if there's any way to change it. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 14:13, 9 December 2025 (UTC)
::OK, thanks. What do you think of installing the [https://www.mediawiki.org/wiki/Extension:CirrusSearch Cirrus search extension]? It seems that Wikimedia is using this by default, and it comes with fuzzy search support, AFAICS. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 14:47, 9 December 2025 (UTC)
:::It looks like there is no opensearch package in Fedora, and honestly I'm not too keen on setting up a tool as large and complex as MediaWiki itself requiring its own systemd services and networks ports and so on if it's only for the sake of this autocompletion… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:20, 12 December 2025 (UTC)

== More fonts for the Wiki ==

Jean,

please have a look at the snippet [[Changing the default text font family]]: as can be seen, some font shapes for DejaVu Mono are missing. Is it possible to get them added to the server that runs the Wiki?

BTW, the same holds for the [[UTF-8]] snippet, where Japanese is missing.
-- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 15:39, 12 December 2025 (UTC)

:Fixed. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:34, 12 December 2025 (UTC)
::Thanks, but are you sure that the CJK font is working correctly? I tried to modify the [[UTF-8]] snippet to trigger a re-rendering, but I still can't see any Japanese... -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 20:44, 12 December 2025 (UTC)
:::Oops, indeed. But I don't understand why. On the server, <code>-dshow-available-fonts</code> does list "Noto Serif CJK JP". And curiously, if I remove all font settings and compile the code with different versions, it starts working between 2.25.12 and 2.25.13. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 23:49, 12 December 2025 (UTC)
::::Ah, I forgot that Google added Font Variation (VF) versions of the CJK fonts, and the various GNU/Linux distros eagerly took them to make the font bundles much smaller. Older LilyPond versions cannot reject these fonts correctly.
::::For me it works with 2.24.4 if you use the font <code>[https://github.com/notofonts/noto-cjk/blob/main/Serif/OTF/Japanese/NotoSerifCJKjp-Regular.otf NotoSerifCJKjp-Regular.otf]</code> (probably also installing the [https://github.com/notofonts/noto-cjk/blob/main/Serif/OTF/Japanese/NotoSerifCJKjp-Bold.otf bold version] for completeness), and this font is found first. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 04:24, 13 December 2025 (UTC)
:::::Thanks, I've added these fonts on the server as a workaround. The snippet now displays correctly. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 09:13, 13 December 2025 (UTC)
::::::Great, thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 10:50, 13 December 2025 (UTC)

== This wiki has no templates ==

Would it be ok if I created some templates? And I am missing several AddOns, CharInsert would be nice for editing, SyntaxHighlight, Scribunto. I am running a rather private Lilypond Wiki in German for several years and have some experience with Wikis, [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 15:13, 18 December 2025 (UTC)

:Feel free to create all kinds of pages, including templates. However, I'd prefer if they were created as needed for specific pages (i.e., don't create templates "for the future" that aren't used on any pages). Also, I don't see much that could be factored between pages so what's your use case? In particular, please don't create templates similar [[wikipedia:Template:Em|<code><nowiki>{{em|...}}</nowiki></code> on Wikipedia]] that add friction to the editing process for a negligible payoff.
:I haven't installed the extensions you requested because:
:# I don't see any special characters that would be needed particularly often on this wiki specifically, and I'd rather not maintain a general list of special characters, this is the job of system-level input methods like Compose keys and character map apps IMHO.
:# It wouldn't make much sense to have syntax highlighting only for the few code snippets that use <code><nowiki><pre></nowiki></code>, as opposed to <code><nowiki><lilypond></nowiki></code>. However, if someone submits a change for adding syntax highlighting to the output of <code><nowiki><lilypond></nowiki></code> in the [https://gitlab.com/jeanas/LilyWiki extension] that defines this tag for the wiki, I'll be happy to review it.
:# Scribunto has security implications (e.g., the need to keep Lua updated), so I'd rather only install it if there is a compelling use case for that.
:[[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 21:10, 18 December 2025 (UTC)
::Thank you for your answer. You have a point with security issues, SyntaxHighlight needs Scribunto. There is no special language support for Lilypond anyway, I use Latex, better than nothing. Your installation has to offer proc open, otherwise Scribunto is not working. I have not found a single provider which allows this.
::Maybe I am missing something in my preferences, when editing I do not see anything that supports editing, not even the option to insert links, maybe it's because I don't use the visual editor, I like "pure" editing as it is in Lilypond. CharInsert offers support for Wiki syntax, including tags like <pre>, all combinations of {} and so on.
::Greetings from Austria, [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 03:17, 19 December 2025 (UTC)
:::[off-topic] Where in Austria? Greetings from Kufstein :-) -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:15, 19 December 2025 (UTC)
::::Niederösterreich, nordöstlich von Wien (Bezirk Gänserndorf) [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 15:21, 19 December 2025 (UTC)
:::I don't think SyntaxHighlight needs Scribunto. It uses Pygments, which is a Python (not Lua) library (of which I actually am technically a maintainer, although I've been inactive lately by lack of time). It certainly needs something like <code>exec</code>/<code>proc_open</code>, but this wiki doesn't use a "managed" MediaWiki install (where the provider installs things for you, à la "Wordpress in one click"), it's on a VPS on which I have root access and administrate things myself, so I can install and configure anything (and <code>exec</code> is already being used to run LilyPond). The real problem is that the LilyPond code snippets are mostly added through a the special, non-standard parser tag <code><nowiki><lilypond></nowiki></code> and so the extension I wrote that defines this tag would need to support syntax highlighting.
:::Regarding the editor toolbar, it sounds like what you want is not CharInsert but [https://www.mediawiki.org/wiki/Extension:WikiEditor WikiEditor], which I've just added. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:15, 19 December 2025 (UTC)
::::PS: I also meant to write that Pygments supports LilyPond. (I implemented this a few years ago.) [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:26, 19 December 2025 (UTC)
:::::Apropos Pygments: I've submitted a [https://github.com/pygments/pygments/pull/2974 PR] to update LilyPond support some time ago. [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:38, 19 December 2025 (UTC)
::::Thank you for installing this extension, this is definitely an improvement. CharInsert is a different animal. Root access is of course best, but you have to do much administration. Usually root access is very expensive when you need a provider. A long time ago I have written a Lilypond extension myself on a home server in my local network.
::::Just in case you are asking who I am, I wrote LSR 1040, 1042, 1043, 1044 (when I remember right) and was involved in 1066 and 1067. [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 19:34, 19 December 2025 (UTC)
:::::I've discovered a potential reason for activating Scribunto: Right now, I'm using the <code>query</code> MediaWiki API to download snippets for <code>makelsr.pl</code>. However, <code>query</code> doesn't expand templates. This means that I have to call the <code>expandtemplates</code> API, sending the unexpanded page to the Wiki server to get an expanded version back.
:::::The Skribunto interface provides [https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#frame:preprocess <code>frame:preprocess</code>], which seems to unify the abovementioned two calls into a single one (I haven't tested it). Maybe this can be configured to not use Lua, in case this simplifies things. What do you think? -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 14:56, 1 January 2026 (UTC)
::::::I don't see a problem with one extra API call per page to expand templates. Also, the function you link is a Lua API, for use in Lua modules running on the wiki, so I don't get how you want to use it outside. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 22:02, 1 January 2026 (UTC)
:::::::OK, <code>expandtemplates</code> it is then :-) -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 23:30, 1 January 2026 (UTC)

== MediaWiki variables for current stable and unstable LilyPond versions ==

Jean,

what do you think about adding [https://www.mediawiki.org/wiki/Manual:Variable MediaWiki variables] that indicate the current stable and unstable LilyPond versions (without the ‘micro’ value)? I suggest

<nowiki>{{LILYSTABLE}}</nowiki> → 2.24
<nowiki>{{LILYDEVEL}}</nowiki> → 2.25

and maybe

<nowiki>{{LILYSTABLEDOC}} → https://lilypond.org/docs/{{LILYSTABLE}}/Documentation</nowiki>
<nowiki>{{LILYDEVELDOC}} → https://lilypond.org/docs/{{LILYDEVEL}}/Documentation</nowiki>

Such variables would reduce maintainance of yet-to-be-written templates. In particular, I would like to add <code><nowiki>Template:convert-ly</nowiki></code>: it would tell users that the snippet in question needs conversion with <code>convert-ly</code> (showing a link to the documentation) for newer versions. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:46, 28 December 2025 (UTC)

:Sounds OK to me. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:34, 28 December 2025 (UTC)
::Great! However, it seems to me that you have to add some piece of PHP code to do that... This means I cannot do it by myself. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 07:00, 30 December 2025 (UTC)
:::Ah, do you need them to be variables as opposed to templates? [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:30, 30 December 2025 (UTC)
::::Do I? I honestly don't know. Please advise. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 12:36, 30 December 2025 (UTC)
:::::Please try templates first. Seems to me that the use case for variables is when you want programmatically generated stuff like the current date. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 19:40, 30 December 2025 (UTC)
::::::It seems to work fine, thanks! However, for more serious template handling I think that the [https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions ParserFunctions] extension would be necessary. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 06:43, 31 December 2025 (UTC)
:::::::Added. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:01, 31 December 2025 (UTC)
::::::::Thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 14:41, 1 January 2026 (UTC)

== Spam users ==

Jean, what shall we do with spam users like User:JoleenStallings? Shall we remove them immediately? While they don't do harm to the Wiki, they are still polluting the namespace... -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:21, 11 January 2026 (UTC)

:Yes. I've just removed all their user pages and blocked them and their IP addresses. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 13:57, 11 January 2026 (UTC)
::OK, thanks. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 16:03, 11 January 2026 (UTC)
:::Obviously the spammers have discovered this wiki. IMHO there is only one solution. Creation of new users only with verification of an admin and editing only for registered users [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 19:53, 11 January 2026 (UTC)
::::Well, it's not that bad: currently, the situation can be handled manually quite easily (by watching the atom feed of this Wiki and quickly removing spam users). However, if this becomes too much of a burden, some additional measures must be taken. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:17, 12 January 2026 (UTC)
:::::OK, this has become too much of a burden at this point, there are several users to block per day. I've added a simple anti-spam question which editors creating an account must solve ("What is the LilyPond command to set a time signature of 3/4?"), let's see how effective this is. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 13:14, 23 February 2026 (UTC)

Talk:Displaying LilyPond's data directory

2026-02-19T15:13:22Z

Jean Abou Samra:

== No LilyPond tag on scheme code ==

I purposely did not use the <code><lilypond></code> tag on this code because I didn't want to expose the Wiki's internal structure. If I'm being overly paranoid we can add it later. [[User:Ksnortum|Ksnortum]] ([[User talk:Ksnortum|talk]]) 16:42, 18 February 2026 (UTC)

:Printing the path inside the wiki wouldn't be a problem, but you can't use <code><nowiki><lilypond></nowiki></code> because it doesn't support snippets which don't produce any visual output. I think giving an error in this case is the right default for <code><nowiki><lilypond></nowiki></code> because we want to remind editors that snippets should come with examples, but adding a <code>no-output</code> option to <code><nowiki><lilypond></nowiki></code> could be sensible. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 15:12, 19 February 2026 (UTC)

Talk:Displaying LilyPond's data directory

2026-02-19T15:12:52Z

Jean Abou Samra: /* No LilyPond tag on scheme code */ Reply

== No LilyPond tag on scheme code ==

I purposely did not use the <code><lilypond></code> tag on this code because I didn't want to expose the Wiki's internal structure. If I'm being overly paranoid we can add it later. [[User:Ksnortum|Ksnortum]] ([[User talk:Ksnortum|talk]]) 16:42, 18 February 2026 (UTC)

:Printing the path inside the wiki wouldn't be a problem, but you can't use <code><nowiki><lilypond></nowiki></code> because it doesn't support snippets which don't produce any visual output. I think giving an error is the right default for <code><nowiki><lilypond></nowiki></code> because we want to remind editors that snippets should come with examples, but adding a <code>no-output</code> to <code><nowiki><lilypond></nowiki></code> could be sensible. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 15:12, 19 February 2026 (UTC)

Displaying LilyPond's data directory

2026-02-19T15:10:36Z

Jean Abou Samra: Print it to stderr

In [[Frescobaldi]], you can install LilyPond while editing the Settings options. However, it is not always clear what directory LilyPond is installed in.

Using the following code will display LilyPond’s data directory in the LilyPond log.

<pre>
\version "2.24"

#(ly:message "The LilyPond data directory is located at: ~a" (ly:get-option 'datadir))
</pre>

(Thanks to Mark Knoop for this code.)

[[Category:Snippet]]
[[Category:Scheme]]

Box around notes

2026-02-02T21:36:05Z

Jean Abou Samra:

This snippet demonstrates how to add boxes around/behind notes. Boxes are automatically sized.

<lilypond version="2.24">
#(define-event-class 'music-boxer-event 'span-event)

#(define-event-class 'box-event 'music-event)

#(define (add-grob-definition grob-name grob-entry)
(set! all-grob-descriptions
(cons ((@@ (lily) completize-grob-entry)
(cons grob-name grob-entry))
all-grob-descriptions)))

#(add-grob-definition
'LyricWord
`(;(stencil . ,ly:lyric-word::print)
(meta . ((class . Spanner)
(interfaces . (lyric-hyphen-interface
lyric-word-interface
text-interface))))))

#(define (make-box thick padding xext yext)
(let ((xext (interval-widen xext padding))
(yext (interval-widen yext padding)))
(ly:stencil-add
(make-filled-box-stencil xext (cons (- (car yext) thick) (car yext)))
(make-filled-box-stencil xext (cons (cdr yext) (+ (cdr yext) thick)))
(make-filled-box-stencil (cons (cdr xext) (+ (cdr xext) thick)) yext)
(make-filled-box-stencil (cons (- (car xext) thick) (car xext)) yext))))

#(define (music-boxer-stencil grob)
(let* ((elts (ly:grob-object grob 'elements))
(refp-X (ly:grob-common-refpoint-of-array grob elts X))
(X-ext (ly:relative-group-extent elts refp-X X))
(refp-Y (ly:grob-common-refpoint-of-array grob elts Y))
(Y-ext (ly:relative-group-extent elts refp-Y Y))
(padding (ly:grob-property grob 'padding 0.3))
(stil (make-box 0.1 padding X-ext Y-ext))
(offset (ly:grob-relative-coordinate grob refp-X X)))
(ly:stencil-translate-axis stil (- offset) X)))

#(define box-stil music-boxer-stencil)

#(add-grob-definition
'Box
`(
(stencil . ,box-stil)
(meta . ((class . Item)
(interfaces . ())))))

#(add-grob-definition
'MusicBoxer
`(
(stencil . ,music-boxer-stencil)
(meta . ((class . Spanner)
(interfaces . ())))))

#(define box-types
'(
(BoxEvent
. ((description . "A box encompassing music at a single timestep.")
(types . (general-music box-event music-event event))
))
))

#(define music-boxer-types
'(
(MusicBoxerEvent
. ((description . "Used to signal where boxes encompassing music start and stop.")
(types . (general-music music-boxer-event span-event event))
))
))

#(set!
music-boxer-types
(map (lambda (x)
(set-object-property! (car x)
'music-description
(cdr (assq 'description (cdr x))))
(let ((lst (cdr x)))
(set! lst (assoc-set! lst 'name (car x)))
(set! lst (assq-remove! lst 'description))
(hashq-set! music-name-to-property-table (car x) lst)
(cons (car x) lst)))
music-boxer-types))

#(set!
box-types
(map (lambda (x)
(set-object-property! (car x)
'music-description
(cdr (assq 'description (cdr x))))
(let ((lst (cdr x)))
(set! lst (assoc-set! lst 'name (car x)))
(set! lst (assq-remove! lst 'description))
(hashq-set! music-name-to-property-table (car x) lst)
(cons (car x) lst)))
box-types))

#(set! music-descriptions
(append music-boxer-types music-descriptions))

#(set! music-descriptions
(append box-types music-descriptions))

#(set! music-descriptions
(sort music-descriptions alist<?))

#(define (add-bound-item spanner item)
(if (null? (ly:spanner-bound spanner LEFT))
(ly:spanner-set-bound! spanner LEFT item)
(ly:spanner-set-bound! spanner RIGHT item)))

musicBoxerEngraver =
#(lambda (context)
(let ((span '())
(finished '())
(current-event '())
(event-start '())
(event-stop '()))

`((listeners
(music-boxer-event .
,(lambda (engraver event)
(if (= START (ly:event-property event 'span-direction))
(set! event-start event)
(set! event-stop event)))))

(acknowledgers
(note-column-interface .
,(lambda (engraver grob source-engraver)
(if (ly:spanner? span)
(begin
(ly:pointer-group-interface::add-grob span 'elements grob)
(add-bound-item span grob)))
(if (ly:spanner? finished)
(begin
(ly:pointer-group-interface::add-grob finished 'elements grob)
(add-bound-item finished grob)))))

(inline-accidental-interface .
,(lambda (engraver grob source-engraver)
(if (ly:spanner? span)
(begin
(ly:pointer-group-interface::add-grob span 'elements grob)))
(if (ly:spanner? finished)
(ly:pointer-group-interface::add-grob finished 'elements grob))))

(script-interface .
,(lambda (engraver grob source-engraver)
(if (ly:spanner? span)
(begin
(ly:pointer-group-interface::add-grob span 'elements grob)))
(if (ly:spanner? finished)
(ly:pointer-group-interface::add-grob finished 'elements grob))))

(finger-interface .
,(lambda (engraver grob source-engraver)
(if (ly:spanner? span)
(begin
(ly:pointer-group-interface::add-grob span 'elements grob)))
(if (ly:spanner? finished)
(ly:pointer-group-interface::add-grob finished 'elements grob))))

;; add additional interfaces to acknowledge here

)

(process-music .
,(lambda (trans)
(if (ly:stream-event? event-stop)
(if (null? span)
(ly:warning "No start to this box.")
(begin
(set! finished span)
(ly:engraver-announce-end-grob trans finished event-start)
(set! span '())
(set! event-stop '()))))
(if (ly:stream-event? event-start)
(begin
(set! span (ly:engraver-make-grob trans 'MusicBoxer event-start))
(set! event-start '())))))

(stop-translation-timestep .
,(lambda (trans)
(if (and (ly:spanner? span)
(null? (ly:spanner-bound span LEFT)))
(ly:spanner-set-bound! span LEFT
(ly:context-property context 'currentMusicalColumn)))
(if (ly:spanner? finished)
(begin
(if (null? (ly:spanner-bound finished RIGHT))
(ly:spanner-set-bound! finished RIGHT
(ly:context-property context 'currentMusicalColumn)))
(set! finished '())
(set! event-start '())
(set! event-stop '())))))

(finalize
(lambda (trans)
(if (ly:spanner? finished)
(begin
(if (null? (ly:spanner-bound finished RIGHT))
(set! (ly:spanner-bound finished RIGHT)
(ly:context-property context 'currentMusicalColumn)))
(set! finished '())))
(if (ly:spanner? span)
(begin
(ly:warning "unterminated box :-(")
(ly:grob-suicide! span)
(set! span '()))))))))

boxEngraver =
#(lambda (context)
(let ((box '())
(ev '()))

`((listeners
(box-event .
,(lambda (engraver event)
(set! ev event))))

(acknowledgers
(note-column-interface .
,(lambda (engraver grob source-engraver)
(if (ly:grob? box)
(begin
; (set! (ly:grob-parent box X) grob) ;; ??
(set! (ly:grob-parent box Y) grob)
(ly:pointer-group-interface::add-grob box 'elements grob)))))

(inline-accidental-interface .
,(lambda (engraver grob source-engraver)
(if (ly:item? box)
(ly:pointer-group-interface::add-grob box 'elements grob))))

(script-interface .
,(lambda (engraver grob source-engraver)
(if (ly:item? box)
(ly:pointer-group-interface::add-grob box 'elements grob))))

(finger-interface .
,(lambda (engraver grob source-engraver)
(if (ly:item? box)
(ly:pointer-group-interface::add-grob box 'elements grob))))

;; add additional interfaces to acknowledge here

)

(process-music .
,(lambda (trans)
(if (ly:stream-event? ev)
(begin
(set! box (ly:engraver-make-grob trans 'Box ev))
(set! ev '())))))
(stop-translation-timestep .
,(lambda (trans)
(set! box '()))))))

musicBoxerStart =
#(make-span-event 'MusicBoxerEvent START)

musicBoxerEnd =
#(make-span-event 'MusicBoxerEvent STOP)

box = #(make-music 'BoxEvent)

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% EXAMPLE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

melody = \relative c'' {
\set fingeringOrientations = #'(left)
%1
\repeat volta 2 {
\once\override Score.Box.padding = 0.5
\box <g-3 c-2 f-1>1
\musicBoxerStart d8-4 g,-0 d' g, d'-4 g,-0 d' \musicBoxerEnd g,
}

%2
\repeat volta 2 {
\box <d'-4 c'-2 f-1>1\f\fermata
\musicBoxerStart g8-3 d-0 g d g8-4 d-0 g \musicBoxerEnd d\accent
}
}

\score {
\new Staff \melody
}

\layout {
\context {
\Global
\grobdescriptions #all-grob-descriptions
}
\context {
\Score
\consists \musicBoxerEngraver % for spans
\consists \boxEngraver
}
}
</lilypond>

[[Category:Education]]
[[Category:Editorial annotations]]
[[Category:Paper and layout]]
[[Category:Scheme]]
[[Category:Specific notation]]
[[Category:Snippet]]

Grouping contexts

2026-02-02T21:35:17Z

Jean Abou Samra:

In polyphonic notation, many voices can share a staff: In this situation, the accidentals and staff are shared, but the stems, slurs, beams, etc., are private to each voice. Hence, engravers should be grouped. The engravers for note head, stems, slurs, etc., go into a group called “Voice context”, while the engravers for key, accidental, bar, etc., go into a group called “Staff context”. In the case of polyphony, a single Staff context contains more than one Voice context. Similarly, more Staff contexts can be put into a single Score context.

<lilypond version="2.24">
topVoice = \relative c' {
\key d\major
es8([ g] a[ fis])
b4
b16[-. b-. b-. cis-.]
d4->
}

botVoice = \relative c' {
\key d\major
c8[( f] b[ a)]
es4
es16[-. es-. es-. fis-.]
b4->
}

hoom = \relative c {
\key d \major
\clef bass
g8-. r
r4
fis8-.
r8
r4
b'4->
}

pah = \relative c' {
r8 b-.
r4
r8 g8-.
r16 g-. r8
\clef treble
fis'4->
}

\score {
\new Staff << \topVoice \\ \botVoice >>
}

\score {
<<
\new Staff << \topVoice \\ \botVoice >>
\new Staff << \pah \\ \hoom >>
>>
}
</lilypond>

[[Category:Rhythms]]
[[Category:Contexts and engravers]]
[[Category:Real music]]
[[Category:Snippet]]

LSR 382

2026-02-01T18:39:44Z

Jean Abou Samra: Shortcut double redirect

#REDIRECT [[Slanted parentheses around dynamics]]

Talk:Slanted parentheses around dynamics

2026-02-01T18:38:20Z

Jean Abou Samra: /* Is this Snippet Necessary? */ Reply

== Is this Snippet Necessary? ==

Can't this be done without Scheme code?

<lilypond version="2.24">
\relative c'' {
\override Parentheses.font-size = #2
c4\parenthesize\f c c \dynamicUp c\parenthesize\p
}
</lilypond>

-- [[User:Ksnortum|Ksnortum]] ([[User talk:Ksnortum|talk]]) 16:52, 31 January 2026 (UTC)

:IMHO the answer is no. <code>\parenthesize</code> doesn't allow the fine-tuning necessary to get good output with slanted text. It might sense, however, to improve the documentation, mentioning <code>\parenthesize</code>. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 06:17, 1 February 2026 (UTC)
::Should I add my code to the snippet, or create an issue on the documentation? [[User:Ksnortum|Ksnortum]] ([[User talk:Ksnortum|talk]]) 15:25, 1 February 2026 (UTC)
:::Please directly modify the snippet. The next Wiki import eventually updates the LilyPond documentation. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 15:35, 1 February 2026 (UTC)
::::Knute, the change itself looks good, thanks. However, the form must be adjusted to follow the guidelines in [[:Category:Included in the official documentation]]: only a single <code><nowiki><lilypond></nowiki></code> block is allowed for ‘official’ snippets. Please fix that. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:03, 1 February 2026 (UTC)
:::::Fixed. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:38, 1 February 2026 (UTC)

Slanted parentheses around dynamics

2026-02-01T18:38:12Z

Jean Abou Samra: Conform to the format of snippets included in the official documentation

The easiest way to parenthesize dynamics is to use the normal <code>\parenthesize</code> command and adjust the font size, e.g., <code>{ c'4\tweak Parentheses.font-size 2 \parenthesize \f }</code>. However, this results in upright parentheses, while dynamic marks are normally slanted. This snippet gives a method to make the parentheses slanted as well.

<lilypond version="2.24">
paren =
#(define-event-function (dyn) (ly:event?)
(make-dynamic-script
#{ \markup \concat {
\normal-text \italic \fontsize #2 (
\pad-x #0.2 #(ly:music-property dyn 'text)
\normal-text \italic \fontsize #2 )
}
#}))

\relative c'' {
c4\paren\f c c \dynamicUp c\paren\p
}
</lilypond>

[[Category:Expressive marks]]
[[Category:Scheme]]
[[Category:Text]]
[[Category:Workaround]]
[[Category:Included in the official documentation]]
[[Category:Snippet]]

Talk:Creating “real” parenthesized dynamics

2026-02-01T18:31:58Z

Jean Abou Samra: Jean Abou Samra moved page Talk:Creating “real” parenthesized dynamics to Talk:Slanted parentheses around dynamics

#REDIRECT [[Talk:Slanted parentheses around dynamics]]

Talk:Slanted parentheses around dynamics

2026-02-01T18:31:58Z

Jean Abou Samra: Jean Abou Samra moved page Talk:Creating “real” parenthesized dynamics to Talk:Slanted parentheses around dynamics

Creating “real” parenthesized dynamics

2026-02-01T18:31:57Z

Jean Abou Samra: Jean Abou Samra moved page Creating “real” parenthesized dynamics to Slanted parentheses around dynamics

#REDIRECT [[Slanted parentheses around dynamics]]

Slanted parentheses around dynamics

2026-02-01T18:31:57Z

Jean Abou Samra: Jean Abou Samra moved page Creating “real” parenthesized dynamics to Slanted parentheses around dynamics

Although the easiest way to add parentheses to a dynamic mark is to use a <code>\markup</code> block, this method has a downside: the created objects behave like text markups and not like dynamics.

However, it is possible to create a similar object using the equivalent Scheme code (as described in the Notation Reference), combined with the <code>make-dynamic-script</code> function. This way, the markup is regarded as a dynamic and therefore remains compatible with commands such as <code>\dynamicUp</code> or <code>\dynamicDown</code>.

<lilypond version="2.24">
paren =
#(define-event-function (dyn) (ly:event?)
(make-dynamic-script
#{ \markup \concat {
\normal-text \italic \fontsize #2 (
\pad-x #0.2 #(ly:music-property dyn 'text)
\normal-text \italic \fontsize #2 )
}
#}))

\relative c'' {
c4\paren\f c c \dynamicUp c\paren\p
}
</lilypond>

Another way to do parenthesize dynamics is to use the <code>\parenthesize</code> command, although this way doesn't give you the fine-tuning of the dynamic text.

<lilypond version="2.24">
\relative c'' {
\override Parentheses.font-size = #2
c4\parenthesize\f c c \dynamicUp c\parenthesize\p
}
</lilypond>

[[Category:Expressive marks]]
[[Category:Scheme]]
[[Category:Text]]
[[Category:Workaround]]
[[Category:Included in the official documentation]]
[[Category:Snippet]]

Smiley

2026-01-31T14:52:27Z

Jean Abou Samra:

Put some funny icons in your score or in a markup. Syntax is <code>\smiley <var>type</var> <var>size</var></code>, or <code>\smileyNoteHead <var>type</var></code>. (Contributed by Pierre-Perol Schneider.)

<lilypond version="2.24">
%%% Smiley defs to be saved as smiley.ily:
lovePath = \markup {
\combine
\override #'(filled . #t)
\with-color #(x11-color 'DeepPink)
\path #0.01
#'((moveto 0.00 0.75)
(curveto 0.00 1.30 0.35 1.90 1.10 1.90)
(curveto 1.50 1.90 1.70 1.75 2.00 1.40)
(curveto 2.30 1.75 2.50 1.90 2.90 1.90)
(curveto 3.65 1.90 4.00 1.30 4.00 0.75)
(curveto 4.00 -0.30 3.00 -0.50 2.05 -1.80)
(curveto 2.00 -1.85 2.00 -1.85 1.95 -1.80)
(curveto 1.00 -0.50 0.00 -0.30 0.00 0.75))
\combine
\path #0.15
#'((moveto 0.00 0.75)
(curveto 0.00 1.30 0.35 1.90 1.10 1.90)
(curveto 1.50 1.90 1.70 1.75 2.00 1.40)
(curveto 2.30 1.75 2.50 1.90 2.90 1.90)
(curveto 3.65 1.90 4.00 1.30 4.00 0.75)
(curveto 4.00 -0.30 3.00 -0.50 2.05 -1.80)
(curveto 2.00 -1.85 2.00 -1.85 1.95 -1.80)
(curveto 1.00 -0.50 0.00 -0.30 0.00 0.75))
\override #'(filled . #t)
\with-color #(x11-color 'LightPink)
\path #0.01
#'((moveto 0.20 0.75)
(curveto 0.20 1.75 1.23 1.84 1.57 1.55)
(curveto 1.05 1.52 0.70 1.10 0.70 0.65)
(curveto 0.70 -0.20 1.30 -0.40 1.86 -1.40)
(curveto 1.10 -0.40 0.20 -0.20 0.20 0.75))
}

smilePath = \markup {
\combine
\override #'(filled . #t)
\with-color #(x11-color 'gold)
\path #0.01
#'((moveto 0.00 0.00)
(curveto 0.00 1.10 0.90 1.82 1.82 1.82)
(curveto 2.70 1.82 3.63 1.10 3.63 0.00)
(curveto 3.63 -1.10 2.70 -1.82 1.82 -1.82)
(curveto 0.91 -1.82 0.00 -1.10 0.00 0.00))
\combine
\path #0.15
#'((moveto 0.00 0.00)
(curveto 0.00 1.10 0.90 1.82 1.82 1.82)
(curveto 2.70 1.82 3.63 1.10 3.63 0.00)
(curveto 3.63 -1.10 2.70 -1.82 1.82 -1.82)
(curveto 0.91 -1.82 0.00 -1.10 0.00 0.00)
(moveto 0.40 -0.13)
(curveto 0.44 -0.10 0.58 -0.04 0.73 -0.09)
(moveto 0.56 -0.08)
(curveto 0.65 -1.63 3.00 -1.63 3.06 -0.07)
(moveto 2.90 -0.07)
(curveto 2.95 -0.06 3.09 -0.04 3.22 -0.12))
\override #'(filled . #t)
\path #0.01
#'((moveto 1.34 1.23)
(curveto 1.61 1.23 1.61 0.17 1.34 0.17)
(curveto 1.09 0.17 1.09 1.23 1.34 1.23)
(moveto 2.31 1.23)
(curveto 2.58 1.23 2.59 0.17 2.31 0.17)
(curveto 2.06 0.17 2.06 1.23 2.31 1.23))
}

winkPath = \markup {
\combine
\override #'(filled . #t)
\with-color #(x11-color 'gold)
\path #0.01
#'((moveto 0.00 0.00)
(curveto 0.00 1.10 0.90 1.82 1.82 1.82)
(curveto 2.70 1.82 3.63 1.10 3.63 0.00)
(curveto 3.63 -1.10 2.70 -1.82 1.82 -1.82)
(curveto 0.91 -1.82 0.00 -1.10 0.00 0.00))
\combine
\path #0.15
#'((moveto 0.00 0.00)
(curveto 0.00 1.10 0.90 1.82 1.82 1.82)
(curveto 2.70 1.82 3.63 1.10 3.63 0.00)
(curveto 3.63 -1.10 2.70 -1.82 1.82 -1.82)
(curveto 0.91 -1.82 0.00 -1.10 0.00 0.00)
(moveto 0.40 -0.13)
(curveto 0.44 -0.10 0.58 -0.04 0.73 -0.09)
(moveto 0.56 -0.08)
(curveto 0.65 -1.63 3.00 -1.63 3.06 -0.07)
(moveto 2.90 -0.07)
(curveto 2.95 -0.06 3.09 -0.04 3.22 -0.12)
(moveto 2.00 0.50)
(curveto 2.10 0.60 2.20 0.80 2.60 0.70)
(moveto 2.00 0.50)
(curveto 2.10 0.50 2.20 0.70 2.60 0.50))
\override #'(filled . #t)
\path #0.01
#'((moveto 1.34 1.23)
(curveto 1.61 1.23 1.61 0.17 1.34 0.17)
(curveto 1.09 0.17 1.09 1.23 1.34 1.23))
}

straitPath = \markup {
\combine
\override #'(filled . #t)
\with-color #(x11-color 'gold)
\path #0.01
#'((moveto 0.00 0.00)
(curveto 0.00 1.10 0.90 1.82 1.82 1.82)
(curveto 2.70 1.82 3.63 1.10 3.63 0.00)
(curveto 3.63 -1.10 2.70 -1.82 1.82 -1.82)
(curveto 0.91 -1.82 0.00 -1.10 0.00 0.00))
\combine
\path #0.15
#'((moveto 0.00 0.00)
(curveto 0.00 1.10 0.90 1.82 1.82 1.82)
(curveto 2.70 1.82 3.63 1.10 3.63 0.00)
(curveto 3.63 -1.10 2.70 -1.82 1.82 -1.82)
(curveto 0.91 -1.82 0.00 -1.10 0.00 0.00))
\combine
\override #'(filled . #t)
\path #0.01
#'((moveto 1.34 1.23)
(curveto 1.61 1.23 1.61 0.17 1.34 0.17)
(curveto 1.09 0.17 1.09 1.23 1.34 1.23)
(moveto 2.31 1.23)
(curveto 2.58 1.23 2.59 0.17 2.31 0.17)
(curveto 2.06 0.17 2.06 1.23 2.31 1.23))
\path #0.2
#'((moveto 1.14 -0.65)
(lineto 2.51 -0.65))
}

eiffelPath = \markup {
\combine
\override #'(filled . #t)
\with-color #(x11-color 'burlywood)
\path #0.01
#'((moveto -0.05 0.00)
(lineto 0.71 0.99)
(lineto 1.04 0.99)
(lineto 0.96 1.36)
(lineto 0.78 1.36)
(lineto 0.71 0.99)
(lineto -0.05 0.00)
(lineto 0.35 0.75)
(lineto 0.35 0.83)
(lineto 0.33 0.86)
(lineto 0.33 0.96)
(lineto 0.40 0.96)
(lineto 0.63 1.56)
(lineto 0.60 1.56)
(lineto 0.59 1.62)
(curveto 0.57 1.70 0.58 1.70 0.63 1.70)
(lineto 0.63 1.73)
(lineto 0.66 1.73)
(curveto 0.72 2.30 0.78 2.70 0.79 3.56)
(lineto 0.77 3.60)
(lineto 0.76 3.68)
(lineto 0.78 3.74)
(curveto 0.85 3.75 0.86 3.78 0.87 4.03)
(curveto 0.88 3.78 0.90 3.74 0.96 3.74)
(lineto 0.98 3.68)
(lineto 0.97 3.60)
(lineto 0.95 3.56)
(curveto 0.97 2.70 1.02 2.30 1.08 1.73)
(lineto 1.11 1.73)
(lineto 1.11 1.70)
(curveto 1.17 1.70 1.17 1.70 1.15 1.62)
(lineto 1.14 1.56)
(lineto 1.11 1.56)
(lineto 1.34 0.96)
(lineto 1.41 0.96)
(lineto 1.41 0.86)
(lineto 1.39 0.83)
(lineto 1.39 0.75)
(lineto 1.79 0.00)
(lineto 1.36 0.00)
(curveto 1.36 0.30 1.10 0.51 0.87 0.51)
(curveto 0.60 0.51 0.38 0.30 0.38 0.00)
(lineto -0.05 0.00))
\path #0.08
#'((moveto 0.71 0.99)
(lineto 1.04 0.99)
(lineto 0.96 1.36)
(lineto 0.78 1.36)
(lineto 0.71 0.99)
(moveto -0.05 0.00)
(lineto 0.35 0.75)
(lineto 0.35 0.83)
(lineto 0.33 0.86)
(lineto 0.33 0.96)
(lineto 0.40 0.96)
(lineto 0.63 1.56)
(lineto 0.60 1.56)
(lineto 0.59 1.62)
(curveto 0.57 1.70 0.58 1.70 0.63 1.70)
(lineto 0.63 1.73)
(lineto 0.66 1.73)
(curveto 0.72 2.30 0.78 2.70 0.79 3.56)
(lineto 0.77 3.60)
(lineto 0.76 3.68)
(lineto 0.78 3.74)
(curveto 0.85 3.75 0.86 3.78 0.87 4.03)
(curveto 0.88 3.78 0.90 3.74 0.96 3.74)
(lineto 0.98 3.68)
(lineto 0.97 3.60)
(lineto 0.95 3.56)
(curveto 0.97 2.70 1.02 2.30 1.08 1.73)
(lineto 1.11 1.73)
(lineto 1.11 1.70)
(curveto 1.17 1.70 1.17 1.70 1.15 1.62)
(lineto 1.14 1.56)
(lineto 1.11 1.56)
(lineto 1.34 0.96)
(lineto 1.41 0.96)
(lineto 1.41 0.86)
(lineto 1.39 0.83)
(lineto 1.39 0.75)
(lineto 1.79 0.00)
(lineto 1.36 0.00)
(curveto 1.36 0.30 1.10 0.51 0.87 0.51)
(curveto 0.60 0.51 0.38 0.30 0.38 0.00)
(lineto -0.05 0.00))
}

#(define-markup-command (smiley layout props smiley-choice smiley-size) (string? number?)
"Include a smiley in a text"
(interpret-markup layout props
(cond
((string=? smiley-choice ":)")
#{
\markup
\scale #(cons (* 0.3 smiley-size)(* 0.3 smiley-size))
\smilePath
#})
((string=? smiley-choice ";)")
#{
\markup
\scale #(cons (* 0.3 smiley-size)(* 0.3 smiley-size))
\winkPath
#})
((string=? smiley-choice ":|")
#{
\markup
\scale #(cons (* 0.3 smiley-size)(* 0.3 smiley-size))
\straitPath
#})
((string=? smiley-choice "<3")
#{
\markup
\scale #(cons (* 0.3 smiley-size)(* 0.3 smiley-size))
\lovePath
#})
((string=? smiley-choice "A")
#{
\markup
\scale #(cons (* 0.3 smiley-size)(* 0.3 smiley-size))
\eiffelPath
#})
(else
#{
\markup
\null
#})
)))

%%%% And even put it as a notehead:
smileyNoteHead =
#(define-music-function
(smiley-choice) (string?)
#{
\once\override NoteHead.stencil =
#(lambda (grob) (grob-interpret-markup grob
#{
\markup\smiley $smiley-choice #0.9
#}))
\once\override NoteHead.stem-attachment = #'(1 . -.2)
\once\override Stem.layer = #0
#})

%%%% End smiley.ily:

%%% TESTS %%%%

%\include "smiley.ily"

\markup\concat {
"I" \hspace #.3
\raise #1.2 \smiley #"<3" #3 \hspace #.3
"P" \hspace #-.6
\raise #0.07 \smiley #"A" #4 \hspace #.1
\smallCaps "ris"
}

\score {
\new Staff {
c'1_\markup\smiley #":)" #3
\mark\markup\smiley #":|" #2
\smileyNoteHead #":|" c'4
\smileyNoteHead #":)" a'
\smileyNoteHead #"<3" \tweak stem-attachment #'(0.98 . 0) f'
s8
}
\layout {
indent = 15
\context {
\Staff
instrumentName = \markup\smiley #"A" #5
\once\override TimeSignature.stencil =
#(lambda (grob) (grob-interpret-markup grob
#{ \markup\smiley #";)" #2 #}))
}
}
}
</lilypond>

[[Category:Scheme]]
[[Category:Symbols and glyphs]]
[[Category:Really cool]]
[[Category:Snippet]]

Spacing out percent repeats with hidden notes

2026-01-31T14:37:39Z

Jean Abou Samra:

If you don't like the spacing used for percent repeats, you can enlarge the percent bars by suitably adding hidden notes.

<lilypond version="2.24">
\new Staff <<
\new Voice {
\repeat percent 3 \relative c'' { e e e e }
\repeat percent 3 \relative c'' { e e e e }
}
\new Voice {
s1 s s
s1 \hideNotes \repeat unfold 8 c4 \unHideNotes
}
>>
</lilypond>

[[Category:Repeats]]
[[Category:Spacing]]
[[Category:Symbols and glyphs]]
[[Category:Workaround]]
[[Category:Snippet]]

Coda ahead of a line of its own

2026-01-31T14:29:07Z

Jean Abou Samra: Remove full option

Here the coda is simply engraved as a new score. (Contributed by Pierre Perol-Schneider.)

<lilypond version="2.24">
myMusic = {
\clef F
\key ees\major
\time 5/4
\set Score.currentBarNumber = #42
\bar ""
g8 r r g\p r4 bes8\< r c' r
g8\mf r r g r4 bes,8 r c r
d8-\tweak X-offset #-2.5 \f d4 d a,8 d^> r r4
\bar "||"
\mark\markup\musicglyph "scripts.segno"
\key bes\major
}

myCoda = {
\clef F
\key bes\major
\time 5/4
\set Score.currentBarNumber = #45
\bar ""
d4. d8~ d4 ees8 r f8 r
g4. g,8~g,4 g8 r8 r4
\bar "||"
\key ees\major
c8 r r c r4 ees8 r f r
}

\score {
\new Staff \with {
\omit TimeSignature
}
\myMusic
\layout {
indent = 0
\context {
\Score
\omit TimeSignature
}
}
}

\score {
\new Staff \with {
\omit TimeSignature
instrumentName = \markup\vcenter {
\bold "coda" \fontsize #3 \musicglyph "scripts.coda"
}
}
\myCoda
\layout {
indent = 25
}
}
</lilypond>

[[Category:Repeats]]
[[Category:Editorial annotations]]
[[Category:Workaround]]
[[Category:Snippet]]

Coda ahead of a line of its own

2026-01-31T14:28:43Z

Jean Abou Samra: Remove broken links, move acknowledgement

Here the coda is simply engraved as a new score. (Contributed by Pierre Perol-Schneider.)

<lilypond version="2.24" full>
myMusic = {
\clef F
\key ees\major
\time 5/4
\set Score.currentBarNumber = #42
\bar ""
g8 r r g\p r4 bes8\< r c' r
g8\mf r r g r4 bes,8 r c r
d8-\tweak X-offset #-2.5 \f d4 d a,8 d^> r r4
\bar "||"
\mark\markup\musicglyph "scripts.segno"
\key bes\major
}

myCoda = {
\clef F
\key bes\major
\time 5/4
\set Score.currentBarNumber = #45
\bar ""
d4. d8~ d4 ees8 r f8 r
g4. g,8~g,4 g8 r8 r4
\bar "||"
\key ees\major
c8 r r c r4 ees8 r f r
}

\score {
\new Staff \with {
\omit TimeSignature
}
\myMusic
\layout {
indent = 0
\context {
\Score
\omit TimeSignature
}
}
}

\score {
\new Staff \with {
\omit TimeSignature
instrumentName = \markup\vcenter {
\bold "coda" \fontsize #3 \musicglyph "scripts.coda"
}
}
\myCoda
\layout {
indent = 25
}
}
</lilypond>

[[Category:Repeats]]
[[Category:Editorial annotations]]
[[Category:Workaround]]
[[Category:Snippet]]

Ripped, torn staff-lines

2026-01-31T13:19:05Z

Jean Abou Samra: Shouldn't be full

Here are some macros (contributed by Mark Polesky) which can make a single staff appear as though its right side has been torn off. Two styles are available: the first "erases" the ends of individual staff- lines to different lengths; the second draws a zigzag line and erases everything to its right. Furthermore, the first type is capable of producing tear-patterns at random. Both work by temporarily modifying the <code>BarLine</code> stencil.

<div class="nodoc">
For technical reasons, the zigzag lines don't show up in the Wiki because <code>\postscript</code> only works with LilyPond's PS backend and is neither supported in the SVG (used in this Wiki) nor in the Cairo backend.
</div>


=== STYLE 1 PREFERENCES: ===

* <code>tearWidth</code> ... default is 1 
horizontal distance (measured in staff-spaces) between the end-points of the shortest and longest staff-lines.
* <code>tearXext</code> ... default is '(0 . 0) 
X-extent of the BarLine stencil, NOT including its width. Can be used as "padding" around the stencil, if needed.


=== STYLE 2 PREFERENCES: ===

* <code>zigzagDefaultYext</code> ... default is '(-4 . 4) 
Y-extent of the zigzag BarLine stencil (measured in staff-spaces).
* <code>zigzagDefaultSerrationCount</code> ... default is 5 
Number of "teeth" or "notches" on the zigzag line.
* <code>zigzagTearLineWidth</code> ... default is 0.1 
Width of the zigzag line itself.
* <code>zigzagTearAngle</code> ... default is 90 
Angle (measured in degrees) of kinks in the zigzag line.
* <code>zigzagTearXext</code> ... default is '(0 . 0) 
X-extent of the zigzag BarLine stencil, NOT including its width. Can be used as "padding" around the stencil, if needed.


=== USAGE: ===

see the <code>\score { }</code> block at the end of the file.

<lilypond version="2.24">
%% preferences %%

tearWidth = #1
tearXext = #'(0 . 0)

zigzagDefaultYext = #'(-4 . 4)
zigzagDefaultSerrationCount = #5
zigzagTearLineWidth = #0.1
zigzagTearAngle = #90
zigzagTearXext = #'(0 . 0)

%% start definitions %%

tearGeneric =
#(define-music-function (lengths) (list?)
(let ((x-ext
(lambda (n)
(cons (* (list-ref lengths n) (/ tearWidth 4)) tearWidth)))
(y-ext '(1.5 . 2.5)))

#{
\once \override Staff.BarLine.stencil = #ly:text-interface::print
\once \override Staff.BarLine.text = \markup
\override #'(baseline-skip . 0) \with-color #white
\column {
\filled-box #(x-ext 0) #y-ext #0
\filled-box #(x-ext 1) #y-ext #0
\filled-box #(x-ext 2) #y-ext #0
\filled-box #(x-ext 3) #y-ext #0
\filled-box #(x-ext 4) #y-ext #0
}
\once \override Staff.BarLine.layer = #1
\once \override Staff.BarLine.X-extent =
#`(,(car tearXext) . ,(- (+ (cdr tearXext) tearWidth) 0.1))
\break
#}))

tear =
#(define-music-function () ()
#{
\tearGeneric
#(let loop ((unused '(0 1 2 3 4))
(lengths '()))
(if (= (length lengths) 5)
lengths
(let* ((x (random (length unused)))
(y (- (length unused) x))
(z (list-ref unused x)))
(loop (append (list-tail unused (+ x 1))
(list-tail (reverse unused) y))
(append lengths `(,z))))))
#})

tearCustom =
#(define-music-function (lengths) (list?)
#{ \tearGeneric #lengths #})

zigzagTearCustom =
#(define-music-function (y-ext serrations)
(pair? number?)
(let* ((zigzagTearHeight (- (cdr y-ext) (car y-ext)))
(deg2rad (lambda (x) (* x (/ (* (atan 1) 4) 180))))
(zigzagTearWidth
(/ zigzagTearHeight
serrations
(* (tan (/ (deg2rad zigzagTearAngle) 2)) 2))))
#{
\once \override Staff.BarLine.stencil = #ly:text-interface::print
\once \override Staff.BarLine.text =
\markup \with-dimensions
#`(0 . ,zigzagTearWidth)
#`(,(car y-ext) . ,(cdr y-ext))
\postscript

#(string-append "
/linewidth " (number->string zigzagTearLineWidth) " def
/height " (number->string zigzagTearHeight) " def
/serrations " (number->string serrations) " def
/width " (number->string zigzagTearWidth) " def
/padding " (number->string (cdr zigzagTearXext)) " 2 width mul add def

/serrationHeight height serrations div def
/y0 " (number->string (cdr y-ext)) " def
/xn width def
/yn serrationHeight 2 div neg def

/plotAngle {
xn yn rlineto
xn neg yn rlineto
} def

/plotSerrations {
serrations { plotAngle } repeat
} def

%% whiteout:
1 setgray
linewidth setlinewidth
0 y0 linewidth add moveto %% (whiteout staff-lines when y-exts are integers)
0 y0 lineto
plotSerrations
0 linewidth neg rlineto %% (whiteout staff-lines when y-exts are integers)
padding 0 rlineto
0 height linewidth 2 mul add rlineto %% (account for top and bottom linewidth)
padding neg 0 rlineto
fill stroke

%% draw serrations:
newpath
0 setgray
linewidth setlinewidth
0 y0 moveto
plotSerrations
stroke")

\once \override Staff.BarLine.layer = #1
\once \override Staff.BarLine.X-extent =
#`(,(car zigzagTearXext) .
,(- (+ (cdr zigzagTearXext) zigzagTearWidth) 0.1))
\break
#}))

zigzagTear = \zigzagTearCustom #zigzagDefaultYext #zigzagDefaultSerrationCount

%% end definitions %%

%% example of a custom tear-pattern:
tearRagged = \tearCustom #'(3 1 3 1 3)

music = { g'4 d'' b' d'' }
\header { tagline=##f }
\score {
{
%% random line-lengths:
\music \tear

%% set line-lengths on-the-fly:
\music \tearCustom #'(0 1 2 3 4)

%% define a custom tear-pattern if you want consistency (see above):
\music \tearRagged

%% default zigzag tear:
\music \zigzagTear

%% set zigzag Y-extent and serration-count on-the-fly:
\transpose c c' \music \zigzagTearCustom #'(-4 . 7) #4
}
\layout {
indent = #0
ragged-right = ##t
}
}
</lilypond>

[[Category:Staff notation]]
[[Category:Editorial annotations]]
[[Category:Really cool]]
[[Category:Snippet]]

[[Category:Correction wanted]]

Ripped, torn staff-lines

2026-01-31T13:18:37Z

Jean Abou Samra: Remove broken links, move acknowledgement

Here are some macros (contributed by Mark Polesky) which can make a single staff appear as though its right side has been torn off. Two styles are available: the first "erases" the ends of individual staff- lines to different lengths; the second draws a zigzag line and erases everything to its right. Furthermore, the first type is capable of producing tear-patterns at random. Both work by temporarily modifying the <code>BarLine</code> stencil.

<div class="nodoc">
For technical reasons, the zigzag lines don't show up in the Wiki because <code>\postscript</code> only works with LilyPond's PS backend and is neither supported in the SVG (used in this Wiki) nor in the Cairo backend.
</div>


=== STYLE 1 PREFERENCES: ===

* <code>tearWidth</code> ... default is 1 
horizontal distance (measured in staff-spaces) between the end-points of the shortest and longest staff-lines.
* <code>tearXext</code> ... default is '(0 . 0) 
X-extent of the BarLine stencil, NOT including its width. Can be used as "padding" around the stencil, if needed.


=== STYLE 2 PREFERENCES: ===

* <code>zigzagDefaultYext</code> ... default is '(-4 . 4) 
Y-extent of the zigzag BarLine stencil (measured in staff-spaces).
* <code>zigzagDefaultSerrationCount</code> ... default is 5 
Number of "teeth" or "notches" on the zigzag line.
* <code>zigzagTearLineWidth</code> ... default is 0.1 
Width of the zigzag line itself.
* <code>zigzagTearAngle</code> ... default is 90 
Angle (measured in degrees) of kinks in the zigzag line.
* <code>zigzagTearXext</code> ... default is '(0 . 0) 
X-extent of the zigzag BarLine stencil, NOT including its width. Can be used as "padding" around the stencil, if needed.


=== USAGE: ===

see the <code>\score { }</code> block at the end of the file.

<lilypond version="2.24" full>
%% preferences %%

tearWidth = #1
tearXext = #'(0 . 0)

zigzagDefaultYext = #'(-4 . 4)
zigzagDefaultSerrationCount = #5
zigzagTearLineWidth = #0.1
zigzagTearAngle = #90
zigzagTearXext = #'(0 . 0)

%% start definitions %%

tearGeneric =
#(define-music-function (lengths) (list?)
(let ((x-ext
(lambda (n)
(cons (* (list-ref lengths n) (/ tearWidth 4)) tearWidth)))
(y-ext '(1.5 . 2.5)))

#{
\once \override Staff.BarLine.stencil = #ly:text-interface::print
\once \override Staff.BarLine.text = \markup
\override #'(baseline-skip . 0) \with-color #white
\column {
\filled-box #(x-ext 0) #y-ext #0
\filled-box #(x-ext 1) #y-ext #0
\filled-box #(x-ext 2) #y-ext #0
\filled-box #(x-ext 3) #y-ext #0
\filled-box #(x-ext 4) #y-ext #0
}
\once \override Staff.BarLine.layer = #1
\once \override Staff.BarLine.X-extent =
#`(,(car tearXext) . ,(- (+ (cdr tearXext) tearWidth) 0.1))
\break
#}))

tear =
#(define-music-function () ()
#{
\tearGeneric
#(let loop ((unused '(0 1 2 3 4))
(lengths '()))
(if (= (length lengths) 5)
lengths
(let* ((x (random (length unused)))
(y (- (length unused) x))
(z (list-ref unused x)))
(loop (append (list-tail unused (+ x 1))
(list-tail (reverse unused) y))
(append lengths `(,z))))))
#})

tearCustom =
#(define-music-function (lengths) (list?)
#{ \tearGeneric #lengths #})

zigzagTearCustom =
#(define-music-function (y-ext serrations)
(pair? number?)
(let* ((zigzagTearHeight (- (cdr y-ext) (car y-ext)))
(deg2rad (lambda (x) (* x (/ (* (atan 1) 4) 180))))
(zigzagTearWidth
(/ zigzagTearHeight
serrations
(* (tan (/ (deg2rad zigzagTearAngle) 2)) 2))))
#{
\once \override Staff.BarLine.stencil = #ly:text-interface::print
\once \override Staff.BarLine.text =
\markup \with-dimensions
#`(0 . ,zigzagTearWidth)
#`(,(car y-ext) . ,(cdr y-ext))
\postscript

#(string-append "
/linewidth " (number->string zigzagTearLineWidth) " def
/height " (number->string zigzagTearHeight) " def
/serrations " (number->string serrations) " def
/width " (number->string zigzagTearWidth) " def
/padding " (number->string (cdr zigzagTearXext)) " 2 width mul add def

/serrationHeight height serrations div def
/y0 " (number->string (cdr y-ext)) " def
/xn width def
/yn serrationHeight 2 div neg def

/plotAngle {
xn yn rlineto
xn neg yn rlineto
} def

/plotSerrations {
serrations { plotAngle } repeat
} def

%% whiteout:
1 setgray
linewidth setlinewidth
0 y0 linewidth add moveto %% (whiteout staff-lines when y-exts are integers)
0 y0 lineto
plotSerrations
0 linewidth neg rlineto %% (whiteout staff-lines when y-exts are integers)
padding 0 rlineto
0 height linewidth 2 mul add rlineto %% (account for top and bottom linewidth)
padding neg 0 rlineto
fill stroke

%% draw serrations:
newpath
0 setgray
linewidth setlinewidth
0 y0 moveto
plotSerrations
stroke")

\once \override Staff.BarLine.layer = #1
\once \override Staff.BarLine.X-extent =
#`(,(car zigzagTearXext) .
,(- (+ (cdr zigzagTearXext) zigzagTearWidth) 0.1))
\break
#}))

zigzagTear = \zigzagTearCustom #zigzagDefaultYext #zigzagDefaultSerrationCount

%% end definitions %%

%% example of a custom tear-pattern:
tearRagged = \tearCustom #'(3 1 3 1 3)

music = { g'4 d'' b' d'' }
\header { tagline=##f }
\score {
{
%% random line-lengths:
\music \tear

%% set line-lengths on-the-fly:
\music \tearCustom #'(0 1 2 3 4)

%% define a custom tear-pattern if you want consistency (see above):
\music \tearRagged

%% default zigzag tear:
\music \zigzagTear

%% set zigzag Y-extent and serration-count on-the-fly:
\transpose c c' \music \zigzagTearCustom #'(-4 . 7) #4
}
\layout {
indent = #0
ragged-right = ##t
}
}
</lilypond>

[[Category:Staff notation]]
[[Category:Editorial annotations]]
[[Category:Really cool]]
[[Category:Snippet]]

[[Category:Correction wanted]]

Mozart’s Musikalisches Würfelspiel

2026-01-30T12:55:21Z

Jean Abou Samra: Don't use q across different measures since it doesn't work after reordering

Mozart’s [https://en.wikipedia.org/wiki/Musikalisches_W%C3%BCrfelspiel Musikalisches Würfelspiel] (score [https://imslp.org/wiki/Musikalisches_W%C3%BCrfelspiel,_K.516f_(Mozart,_Wolfgang_Amadeus) available on IMSLP]) is a system to create a waltz by choosing each measure from a list of possibilities, with 759,499,667,166,482 possible waltzes in total. This is an implementation of the Würfelspiel using a bit of Scheme code to select the measures at random, producing a different waltz at each compilation. The code is an instructive example of creating music functions and manipulating music in Scheme.

<lilypond version="2.24">
rhMeasureEight = \relative {
\tag generation \alternative {
\volta 1 { <g' b d g>4 r8 }
\volta 2 { <g b d g>4 r8 }
}
\tag table {
<g b d g>4 r8
}
}

lhMeasureEight = \relative {
\tag generation \alternative {
\volta 1 { g,8 g'16 f! e d }
\volta 2 { g,8 b'16 g fis e }
}
\tag table {
<< { g,8^"Volta 2" b'16 g fis e } \\ { g,8_"Volta 1" g'16 f! e d } >>
}
}

rhData = \relative {
| f''8 d g
| a,8 fis16 g b g'
| g8 c, e
| g8 d4\trill
| \rhMeasureEight
| g,8 c e
| e16 c e g c g
| c,4 r8
| <c e>8 r8
| b16 a b c d b
| e16 c b a g fis
| <e c'>8 8 8
| c'8( g e)
| c'4 r8
| e8 g16 e c8
| a'8( fis d)
| c16 g c e g, c
| g8( c e)
| e16 c e8 g
| g8 b16 d d,8
| c16 e g d a fis'
| e8 c g
| f'16 e d e f g
| \rhMeasureEight
| d,16 fis a d fis a
| <c, e>8 8 8
| f16 e f d c b
| fis'16 d a a' fis d
| b16 d g d b8
| \rhMeasureEight
| e16[ c g8] e'
| g,8 c e
| \rhMeasureEight
| e16 c d b g8
| a8 d fis
| a,16 e' d g fis a
| g16 b g d b8
| c8 g e'
| g8 g, g
| c16 b c e g, c
| c16 b c e g,8
| b16 c d b a g
| g'8 f16 e d c
| a8 f'16 d a b
| c16 b c g e c
| g''8 b16 g d b
| g'8 g16 d b'8
| e,8 c16 e g c
| e,8( c g)
| c8 e16 c g8
| c16 g e' c g' e
| d16( cis) d f g, b
| <c e>8 16 <d f> <e g>8
| <e, c'>8 8 8
| g'8 b d,
| d16 b g8 r8
| e'8 c g
| g'8 e c
| g'8 c, e
| g8 f16 e d c
| c8 e16 c g'8
| e16 c b g a fis
| e'16 c b c g8
| e'16 g c g e c
| d16 a d8 fis
| fis8 a fis
| c16 b c e g, c
| g'8 b16 g d g
| g8( e c)
| fis8 a16 fis d fis
| g16 b d b g8
| f16 e d c b d
| g8 e c
| c'16 b c g e c
| <d fis>8 8 8
| c'16 b c g e c
| g'16 b g8 d
| c8 c, r
| c'4 r8
| d8 a\turn fis'
| \rhMeasureEight
| d16[ b g8] g'
| c,4 r8
| c16 g e' c g' e
| c8 e g,
| d'8 d16 g b8
| g8 c, e
| g16 d g b g d
| f16 e d8 g
| fis16 a d a fis a
| \rhMeasureEight
| <b, d>8 g'16 b d,8
| c4 r8
| \rhMeasureEight
| g'8 e c
| e8 c g
| g'16 fis g d b g
| c8 g e'
| fis8 a d,
| \rhMeasureEight
| e16 d e g c g
| fis16 d a8 fis'
| c16 e c g e8
| e'16 d e g c g
| fis8 a16 fis d fis
| a,8 d16 c b a
| \rhMeasureEight
| e'8( g c)
| d,16 f d f b, d
| 16( <a c>) q( <g b>) q( <fis a>)
| c'4 r8
| e8 c g
| f'8 d b
| 8 q q
| c16 g e' c g' e
| d16 f a f d b
| d16 a d fis a fis
| e16 a g b fis a
| e16 c g' e c' g
| d'8 a16 fis d a
| g'8 b16 g d8
| g16 fis g b d,8
| \rhMeasureEight
| <e, c'>8 8 8
| g'16 e d b g8
| c16 g c e g <c, e>
| \rhMeasureEight
| b8 d g
| a16 g fis g d8
| <e, c'>8 8 8
| c'4 r8
| <c e>8 16 <g b> g8
| d'8 g16 d b d
| a16 e' <a c> <g b> <fis a>
| fis'8 fis16 d a'8
| c16 b c g e c
| c8 g e'
| <a, d fis>8 fis'4\trill
| g16 b g b d,8
| a8 a16 d fis8
| d16 e f d c b
| c8 g e'
| g8 d16 b g8
| g'8 c, e
| d16 f a, d b d
| <fis, d'>8 <d' fis> <fis a>
| e16 c' b g a fis
| c'16 b c g e c
| f16 d a8 b
| <g c e>8 e'4\trill
| c4 r8
| g'8 f16 e d c
| d16 a fis' d a' fis
| d16 cis d fis a fis
| g16 b g d b g
| c16 g e' c g'8
| e16 d e g c g
| b,8 d16 b a g
| e'16 g d c b a
| c16 b c e g, c
| <fis, d'>8 8 8
| e'16 d e g c g
| g16 fis g d b g
| d'8 g,4
| d'8( b g)
| d'16 b' g d b8
| c8 c16 d e8
| g8 f16 e d c
| e16 g d g a, fis'
| c4 r8
| b16 c d e f d
| c4 r8
| f16 a a,8 b16 d
| g,8 c e
| e16 c b d g8
| a16 g b g d g
}

lhData = \relative {
| f8 d g
| <b, g'>4 r8
| <c e>4 r8
| g16 b g'8 b,
| \lhMeasureEight
| <c e>4 r8
| <c g'>4 r8
| c8 g c,
| g''4 g,8
| g'4 r8
| c,8 d d,
| c'8 8 8
| <e g>4 8
| c8 g c,
| <c' g'>4 <c e>8
| <d fis>4 <c fis>8
| <e g>4 r8
| <c e>4 <c g'>8
| <c g'>4 <c e>8
| b4 r8
| c8 d d,
| c'4 r8
| f16 e d e f g
| \lhMeasureEight
| d4 c8
| c16 e g e c' c,
| <g' b>4 r8
| <c, a'>4 r8
| g'4 g,8
| \lhMeasureEight
| <c g'>4 8
| <c e>4 r8
| \lhMeasureEight
| g'4 r8
| <d fis>4 <c a'>8
| c8 d d,
| <b' d>4 r8
| <c e>16 g' q g q g
| b,16 d g d b g
| <c e>4 r8
| <c e>4 r8
| g4 r8
| <c e>4 r8
| f4 g8
| <e g>4 r8
| 4 r8
| 4 r8
| <c g'>4 <c e>8
| <c e>16 g' q g q g
| <e g>4 r8
| <c e>4 r8
| f4 g8
| c,4 r8
| c8 8 8
| 4 r8
| <g g'>4 g'8
| <c, e>16 g' q g q g
| <c, e>16 g' q g q g
| <c, e>16 g' q g q g
| <c, e>4 r8
| <e g>4 r8
| c8 d d,
| c'4 r8
| <c g'>4 8
| <d fis>4 r8
| << { a'8 fis d } \\ { d8 d c } >>
| <c e>4 <e g>8
| b4 r8
| <c e>4 r8
| d4 c8
| 4 8
| f'4 g8
| <c, e>16 g' q g q g
| <c, e>4 r8
| c8 8 8
| <c e>4 <c g'>8
| 4 8
| c4 c,8
| c'8 g c,
| c'4 r8
| \lhMeasureEight
| 4 8
| c8 g c,
| <c' e>4 r8
| <e g>4 r8
| 4 r8
| <c e>4 <c g'>8
| 4 8
| f'16 e d8 g
| <c, a'>4 8
| \lhMeasureEight
| <g g'>4 g'8
| c,8 g c,
| \lhMeasureEight
| <c' e>4 r8
| c4 r8
| 4 8
| <c e>16 g' q g q g
| <c, a'>4 8
| \lhMeasureEight
| <c g'>4 <c e>8
| <c a'>4 8
| <e g>4 r8
| c4 r8
| c4 r8
| c8 d d,
| \lhMeasureEight
| <c' g'>4 <c e>8
| <f a>4 <g d'>8
| c,8 d d,
| c'8 g c,
| <c' e>16 g' q g q g
| <g b>4 r8
| g8 8 8
| <c, e>4 r8
| f4 g8
| <d fis>4 r8
| c8 d d,
| <c' e>4 r8
| <d fis>4 <c fis>8
| 4 r8
| 8 8 
| \lhMeasureEight
| c8 8 8
| g'8 g, r
| e'4 e16 c
| \lhMeasureEight
| g4 r8
| 8 8 
| c8 8 8
| c8 g c,
| g''8 g, r8
| 4 r8
| c8 d d,
| << { d'8 d d } \\ { c8 c c } >>
| << e4 \\ c4 >> r8
| <c e>16 g' q g q g
| d,16 d' cis d c d
| b4 r8
| <c fis>8 8 <c a'>
| 4 g8
| <c e>4 r8
| 4 8
| <c e>16 g' q g q g
| f4 g8
| c,8 8 8
| c8 d d,
| <c' e>4 r8
| f4 g8
| c,16 b c d e fis
| c8 g c,
| <c' e>4 r8
| c4 r8
| c4 r8
| 4 r8
| <e g>4 r8
| c4 r8
| g4 r8
| c8 d d,
| <c' e>4 8
| c8 8 8
| <c g'>4 <c e>8
| 4 r8
| g'16 fis g d b g
| b4 r8
| <g' b>4 r8
| <c, e>4 r8
| <c e>4 <e g>8
| c8 d d,
| c'8 g c,
| <g' g'>4 8
| c8 g c,
| f'4 g8
| <c, e>16 g' q g q g
| g8 g, r8
| 4 8
}

table = #'(
#(96 32 69 40 148 104 152 119 98 3 54)
#(22 6 95 17 74 157 60 84 142 87 130)
#(141 128 158 113 163 27 171 114 42 165 10)
#(41 63 13 85 45 167 53 50 156 61 103)
#(105 146 153 161 80 154 99 140 75 135 28)
#(122 46 55 2 97 68 133 86 129 47 37)
#(11 134 110 159 36 118 21 169 62 147 106)
#(30 81 24 100 107 91 127 94 123 33 5)
#(70 117 66 90 25 138 16 120 65 102 35)
#(121 39 139 176 143 71 155 88 77 4 20)
#(26 126 15 7 64 150 57 48 19 31 108)
#(9 56 132 34 125 29 175 166 82 164 92)
#(112 174 73 67 76 101 43 51 137 144 12)
#(49 18 58 160 136 162 168 115 38 59 124)
#(109 116 145 52 1 23 89 72 149 173 44)
#(14 83 79 170 93 151 172 111 8 78 131)
)

#(define choices
(map (lambda (possibilities)
(1- (vector-ref possibilities (random 11))))
table))

#(define (split-measures music)
(let ((elements (ly:music-property
(ly:music-property music 'element)
'elements)))
(let loop ((elts (reverse elements))
(measure '())
(measures '()))
(cond
((null? elts)
(list->vector measures))
((or (music-is-of-type? (car elts) 'bar-check) ;; until 2.25.5
(music-is-of-type? (car elts) 'bar-check-event)) ;; since 2.25.6
(let ((measure-music (make-sequential-music measure)))
(loop (cdr elts) '() (cons measure-music measures))))
(else
(loop (cdr elts) (cons (car elts) measure) measures))))))

applyChoices =
#(define-music-function (music) (ly:music?)
(let* ((measures (split-measures music))
(chosen-measures
(map (lambda (i) (vector-ref measures i))
choices))
(first-part (make-sequential-music (take chosen-measures 8)))
(second-part (make-sequential-music (drop chosen-measures 8))))
#{
\repeat volta 2 { #first-part }
\repeat volta 2 { #second-part }
#}))

\header {
title = "Valse"
composer = "Mozart"
}

randomWaltz =
\keepWithTag generation
\new PianoStaff <<
\new Staff {
\time 3/8
\applyChoices \rhData
}
\new Staff {
\clef bass
\applyChoices \lhData
}
>>

\score {
\layout { }
\randomWaltz
}

\score {
\midi { }
\unfoldRepeats \randomWaltz
}

% Uncomment to display the table of all possible measures ("Notentafel")
%{
\score {
\layout {
\context {
\Score
barNumberVisibility = #all-bar-numbers-visible
\override BarNumber.break-visibility = #end-of-line-invisible
centerBarNumbers = ##t
}
}
\keepWithTag table <<
\new Staff {
\time 3/8
\rhData
}
\new Staff {
\clef bass
\lhData
}
>>
}
%}
</lilypond>

Talk:Ripped, torn staff-lines

2026-01-29T16:27:58Z

Jean Abou Samra: /* zigzag */ Reply

== zigzag ==

here in the wiki the zigzag lines seem to be omitted. The code itself does work. --[[User:Rudi Guggt|Rudi Guggt]] ([[User talk:Rudi Guggt|talk]]) 09:35, 29 January 2026 (UTC)

:Ja, anscheinend funktionieren mehrere Dinge nicht, wie ich schon bei einem anderen Snippet angemerkt habe. Leider kann man keine Bilder hochladen, um zu illustrieren, wie es sein sollte. Der Bürokrat in diesem Wiki hat die Funktionalität dieses Wikis ziemlich stark eingeschränkt. [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 16:22, 29 January 2026 (UTC)
:This wiki uses SVG output, where <code>\postscript</code> cannot work, as mentioned on [[PostScript lines]]. The snippet should be changed to use markup commands like <code>\path</code>. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:27, 29 January 2026 (UTC)

User talk:Jean Abou Samra

2026-01-11T13:57:23Z

Jean Abou Samra: /* Spam users */ Reply

Demonstrating LilyPond support for figured bass

2026-01-08T13:20:30Z

Jean Abou Samra:

This snippet demonstrates how figured bass is supported in LilyPond. In addition to the numerous BassFigure objects available, you can always use text markups instead to get precisely what you need. 
All of these examples are to be found in the relevant sections of the Notation Reference, where you will learn how to add a figured bass with simple but powerful notation.

<lilypond version="2.24">
<<
\new Voice {
\clef bass
dis4 c d ais
g fis e a
r gis d b,
f,! e c c
c1
}
\figures {
< 6 >4 < 7\+ >8 < 6+ [_!] >
< 6 >4 <6 5 [3+] >
< _ >4 < 6 5/>4
<4- 6+ 7!> <5++> <3--> <7/> r <6\+ 5/>
< [4 6] 8 [_! 12] >
< 5 \markup { \tiny \number 6 \super (1) } >
\set useBassFigureExtenders = ##t
<4 6> <3 6> <3 7>
}
>>
</lilypond>

[[Category:Ancient notation]]
[[Category:Simultaneous notes]]
[[Category:Chords]]
[[Category:Keyboards]]
[[Category:Fretted strings]]
[[Category:Ancient notation]]
[[Category:Snippet]]

Talk:Mozart’s Musikalisches Würfelspiel

2026-01-07T19:34:12Z

Jean Abou Samra: /* Does not work with 2.25 */ Reply

== Volte in wrong order? ==

It seems to me that the prima volta bar should be seconda volta and vice versa. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 15:08, 7 January 2026 (UTC)

:Indeed! Fixed, thanks. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 15:26, 7 January 2026 (UTC)

== Does not work with 2.25 ==

What changed? Compiling with 2.25 produces an error message [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 18:52, 7 January 2026 (UTC)

:Fixed, thanks. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 19:34, 7 January 2026 (UTC)

Mozart’s Musikalisches Würfelspiel

2026-01-07T19:33:51Z

Jean Abou Samra: Make it work in 2.25

Mozart's [https://en.wikipedia.org/wiki/Musikalisches_W%C3%BCrfelspiel Musikalisches Würfelspiel] (score [https://imslp.org/wiki/Musikalisches_W%C3%BCrfelspiel,_K.516f_(Mozart,_Wolfgang_Amadeus) available on IMSLP]) is a system to create a waltz by choosing each measure from a list of possibilities, with 759,499,667,166,482 possible waltzes in total. This is an implementation of the Würfelspiel using a bit of Scheme code to select the measures at random, producing a different waltz at each compilation. The code is an instructive example of creating music functions and manipulating music in Scheme.

<lilypond version="2.24">
rhMeasureEight = \relative {
\tag generation \alternative {
\volta 1 { <g' b d g>4 r8 }
\volta 2 { <g b d g>4 r8 }
}
\tag table {
<g b d g>4 r8
}
}

lhMeasureEight = \relative {
\tag generation \alternative {
\volta 1 { g,8 g'16 f! e d }
\volta 2 { g,8 b'16 g fis e }
}
\tag table {
<< { g,8^"Volta 2" b'16 g fis e } \\ { g,8_"Volta 1" g'16 f! e d } >>
}
}

rhData = \relative {
| f''8 d g
| a,8 fis16 g b g'
| g8 c, e
| g8 d4\trill
| \rhMeasureEight
| g,8 c e
| e16 c e g c g
| c,4 r8
| <c e>8 r8
| b16 a b c d b
| e16 c b a g fis
| <e c'>8 8 8
| c'8( g e)
| c'4 r8
| e8 g16 e c8
| a'8( fis d)
| c16 g c e g, c
| g8( c e)
| e16 c e8 g
| g8 b16 d d,8
| c16 e g d a fis'
| e8 c g
| f'16 e d e f g
| \rhMeasureEight
| d,16 fis a d fis a
| <c, e>8 8 8
| f16 e f d c b
| fis'16 d a a' fis d
| b16 d g d b8
| \rhMeasureEight
| e16[ c g8] e'
| g,8 c e
| \rhMeasureEight
| e16 c d b g8
| a8 d fis
| a,16 e' d g fis a
| g16 b g d b8
| c8 g e'
| g8 g, g
| c16 b c e g, c
| c16 b c e g,8
| b16 c d b a g
| g'8 f16 e d c
| a8 f'16 d a b
| c16 b c g e c
| g''8 b16 g d b
| g'8 g16 d b'8
| e,8 c16 e g c
| e,8( c g)
| c8 e16 c g8
| c16 g e' c g' e
| d16( cis) d f g, b
| <c e>8 16 <d f> <e g>8
| <e, c'>8 8 8
| g'8 b d,
| d16 b g8 r8
| e'8 c g
| g'8 e c
| g'8 c, e
| g8 f16 e d c
| c8 e16 c g'8
| e16 c b g a fis
| e'16 c b c g8
| e'16 g c g e c
| d16 a d8 fis
| fis8 a fis
| c16 b c e g, c
| g'8 b16 g d g
| g8( e c)
| fis8 a16 fis d fis
| g16 b d b g8
| f16 e d c b d
| g8 e c
| c'16 b c g e c
| <d fis>8 8 8
| c'16 b c g e c
| g'16 b g8 d
| c8 c, r
| c'4 r8
| d8 a\turn fis'
| \rhMeasureEight
| d16[ b g8] g'
| c,4 r8
| c16 g e' c g' e
| c8 e g,
| d'8 d16 g b8
| g8 c, e
| g16 d g b g d
| f16 e d8 g
| fis16 a d a fis a
| \rhMeasureEight
| <b, d>8 g'16 b d,8
| c4 r8
| \rhMeasureEight
| g'8 e c
| e8 c g
| g'16 fis g d b g
| c8 g e'
| fis8 a d,
| \rhMeasureEight
| e16 d e g c g
| fis16 d a8 fis'
| c16 e c g e8
| e'16 d e g c g
| fis8 a16 fis d fis
| a,8 d16 c b a
| \rhMeasureEight
| e'8( g c)
| d,16 f d f b, d
| 16( <a c>) q( <g b>) q( <fis a>)
| c'4 r8
| e8 c g
| f'8 d b
| 8 q q
| c16 g e' c g' e
| d16 f a f d b
| d16 a d fis a fis
| e16 a g b fis a
| e16 c g' e c' g
| d'8 a16 fis d a
| g'8 b16 g d8
| g16 fis g b d,8
| \rhMeasureEight
| <e, c'>8 8 8
| g'16 e d b g8
| c16 g c e g <c, e>
| \rhMeasureEight
| b8 d g
| a16 g fis g d8
| <e, c'>8 8 8
| c'4 r8
| <c e>8 16 <g b> g8
| d'8 g16 d b d
| a16 e' <a c> <g b> <fis a>
| fis'8 fis16 d a'8
| c16 b c g e c
| c8 g e'
| <a, d fis>8 fis'4\trill
| g16 b g b d,8
| a8 a16 d fis8
| d16 e f d c b
| c8 g e'
| g8 d16 b g8
| g'8 c, e
| d16 f a, d b d
| <fis, d'>8 <d' fis> <fis a>
| e16 c' b g a fis
| c'16 b c g e c
| f16 d a8 b
| <g c e>8 e'4\trill
| c4 r8
| g'8 f16 e d c
| d16 a fis' d a' fis
| d16 cis d fis a fis
| g16 b g d b g
| c16 g e' c g'8
| e16 d e g c g
| b,8 d16 b a g
| e'16 g d c b a
| c16 b c e g, c
| <fis, d'>8 8 8
| e'16 d e g c g
| g16 fis g d b g
| d'8 g,4
| d'8( b g)
| d'16 b' g d b8
| c8 c16 d e8
| g8 f16 e d c
| e16 g d g a, fis'
| c4 r8
| b16 c d e f d
| c4 r8
| f16 a a,8 b16 d
| g,8 c e
| e16 c b d g8
| a16 g b g d g
}

lhData = \relative {
| f8 d g
| <b, g'>4 r8
| <c e>4 r8
| g16 b g'8 b,
| \lhMeasureEight
| <c e>4 r8
| <c g'>4 r8
| c8 g c,
| g''4 g,8
| g'4 r8
| c,8 d d,
| c'8 8 8
| <e g>4 8
| c8 g c,
| <c' g'>4 <c e>8
| <d fis>4 <c fis>8
| <e g>4 r8
| <c e>4 <c g'>8
| <c g'>4 <c e>8
| b4 r8
| c8 d d,
| c'4 r8
| f16 e d e f g
| \lhMeasureEight
| d4 c8
| c16 e g e c' c,
| <g' b>4 r8
| <c, a'>4 r8
| g'4 g,8
| \lhMeasureEight
| <c g'>4 8
| <c e>4 r8
| \lhMeasureEight
| g'4 r8
| <d fis>4 <c a'>8
| c8 d d,
| <b' d>4 r8
| <c e>16 g' q g q g
| b,16 d g d b g
| <c e>4 r8
| <c e>4 r8
| g4 r8
| <c e>4 r8
| f4 g8
| <e g>4 r8
| 4 r8
| q4 r8
| <c g'>4 <c e>8
| <c e>16 g' q g q g
| <e g>4 r8
| <c e>4 r8
| f4 g8
| c,4 r8
| c8 8 8
| 4 r8
| <g g'>4 g'8
| <c, e>16 g' q g q g
| q16 g q g q g
| q16 g q g q g
| <c, e>4 r8
| <e g>4 r8
| c8 d d,
| c'4 r8
| <c g'>4 8
| <d fis>4 r8
| << { a'8 fis d } \\ { d8 d c } >>
| <c e>4 <e g>8
| b4 r8
| <c e>4 r8
| d4 c8
| 4 8
| f'4 g8
| <c, e>16 g' q g q g
| <c, e>4 r8
| c8 8 8
| <c e>4 <c g'>8
| 4 8
| c4 c,8
| c'8 g c,
| c'4 r8
| \lhMeasureEight
| 4 8
| c8 g c,
| <c' e>4 r8
| <e g>4 r8
| 4 r8
| <c e>4 <c g'>8
| 4 8
| f'16 e d8 g
| <c, a'>4 8
| \lhMeasureEight
| <g g'>4 g'8
| c,8 g c,
| \lhMeasureEight
| <c' e>4 r8
| c4 r8
| 4 8
| <c e>16 g' q g q g
| <c, a'>4 8
| \lhMeasureEight
| <c g'>4 <c e>8
| <c a'>4 8
| <e g>4 r8
| c4 r8
| c4 r8
| c8 d d,
| \lhMeasureEight
| <c' g'>4 <c e>8
| <f a>4 <g d'>8
| c,8 d d,
| c'8 g c,
| <c' e>16 g' q g q g
| <g b>4 r8
| g8 8 8
| <c, e>4 r8
| f4 g8
| <d fis>4 r8
| c8 d d,
| <c' e>4 r8
| <d fis>4 <c fis>8
| 4 r8
| 8 8 
| \lhMeasureEight
| c8 8 8
| g'8 g, r
| e'4 e16 c
| \lhMeasureEight
| g4 r8
| 8 8 
| c8 8 8
| c8 g c,
| g''8 g, r8
| 4 r8
| c8 d d,
| << { d'8 d d } \\ { c8 c c } >>
| << e4 \\ c4 >> r8
| <c e>16 g' q g q g
| d,16 d' cis d c d
| b4 r8
| <c fis>8 8 <c a'>
| 4 g8
| <c e>4 r8
| 4 8
| <c e>16 g' q g q g
| f4 g8
| c,8 8 8
| c8 d d,
| <c' e>4 r8
| f4 g8
| c,16 b c d e fis
| c8 g c,
| <c' e>4 r8
| c4 r8
| c4 r8
| 4 r8
| <e g>4 r8
| c4 r8
| g4 r8
| c8 d d,
| <c' e>4 8
| c8 8 8
| <c g'>4 <c e>8
| 4 r8
| g'16 fis g d b g
| b4 r8
| <g' b>4 r8
| <c, e>4 r8
| <c e>4 <e g>8
| c8 d d,
| c'8 g c,
| <g' g'>4 8
| c8 g c,
| f'4 g8
| <c, e>16 g' q g q g
| g8 g, r8
| 4 8
}

table = #'(
#(96 32 69 40 148 104 152 119 98 3 54)
#(22 6 95 17 74 157 60 84 142 87 130)
#(141 128 158 113 163 27 171 114 42 165 10)
#(41 63 13 85 45 167 53 50 156 61 103)
#(105 146 153 161 80 154 99 140 75 135 28)
#(122 46 55 2 97 68 133 86 129 47 37)
#(11 134 110 159 36 118 21 169 62 147 106)
#(30 81 24 100 107 91 127 94 123 33 5)
#(70 117 66 90 25 138 16 120 65 102 35)
#(121 39 139 176 143 71 155 88 77 4 20)
#(26 126 15 7 64 150 57 48 19 31 108)
#(9 56 132 34 125 29 175 166 82 164 92)
#(112 174 73 67 76 101 43 51 137 144 12)
#(49 18 58 160 136 162 168 115 38 59 124)
#(109 116 145 52 1 23 89 72 149 173 44)
#(14 83 79 170 93 151 172 111 8 78 131)
)

#(define choices
(map (lambda (possibilities)
(1- (vector-ref possibilities (random 11))))
table))

#(define (split-measures music)
(let ((elements (ly:music-property
(ly:music-property music 'element)
'elements)))
(let loop ((elts (reverse elements))
(measure '())
(measures '()))
(cond
((null? elts)
(list->vector measures))
((or (music-is-of-type? (car elts) 'bar-check) ;; until 2.25.5
(music-is-of-type? (car elts) 'bar-check-event)) ;; since 2.25.6
(let ((measure-music (make-sequential-music measure)))
(loop (cdr elts) '() (cons measure-music measures))))
(else
(loop (cdr elts) (cons (car elts) measure) measures))))))

applyChoices =
#(define-music-function (music) (ly:music?)
(let* ((measures (split-measures music))
(chosen-measures
(map (lambda (i) (vector-ref measures i))
choices))
(first-part (make-sequential-music (take chosen-measures 8)))
(second-part (make-sequential-music (drop chosen-measures 8))))
#{
\repeat volta 2 { #first-part }
\repeat volta 2 { #second-part }
#}))

\header {
title = "Valse"
composer = "Mozart"
}

randomWaltz =
\keepWithTag generation
\new PianoStaff <<
\new Staff {
\time 3/8
\applyChoices \rhData
}
\new Staff {
\clef bass
\applyChoices \lhData
}
>>

\score {
\layout { }
\randomWaltz
}

\score {
\midi { }
\unfoldRepeats \randomWaltz
}

% Uncomment to display the table of all possible measures ("Notentafel")
%{
\score {
\layout {
\context {
\Score
barNumberVisibility = #all-bar-numbers-visible
\override BarNumber.break-visibility = #end-of-line-invisible
centerBarNumbers = ##t
}
}
\keepWithTag table <<
\new Staff {
\time 3/8
\rhData
}
\new Staff {
\clef bass
\lhData
}
>>
}
%}
</lilypond>

Talk:Mozart’s Musikalisches Würfelspiel

2026-01-07T15:26:42Z

Jean Abou Samra: /* Volte in wrong order? */ Reply

Mozart’s Musikalisches Würfelspiel

2026-01-07T15:26:11Z

Jean Abou Samra:

Mozart's [https://en.wikipedia.org/wiki/Musikalisches_W%C3%BCrfelspiel Musikalisches Würfelspiel] (score [https://imslp.org/wiki/Musikalisches_W%C3%BCrfelspiel,_K.516f_(Mozart,_Wolfgang_Amadeus) available on IMSLP]) is a system to create a waltz by choosing each measure from a list of possibilities, with 759,499,667,166,482 possible waltzes in total. This is an implementation of the Würfelspiel using a bit of Scheme code to select the measures at random, producing a different waltz at each compilation. The code is an instructive example of creating music functions and manipulating music in Scheme.

<lilypond version="2.24">
rhMeasureEight = \relative {
\tag generation \alternative {
\volta 1 { <g' b d g>4 r8 }
\volta 2 { <g b d g>4 r8 }
}
\tag table {
<g b d g>4 r8
}
}

lhMeasureEight = \relative {
\tag generation \alternative {
\volta 1 { g,8 g'16 f! e d }
\volta 2 { g,8 b'16 g fis e }
}
\tag table {
<< { g,8^"Volta 2" b'16 g fis e } \\ { g,8_"Volta 1" g'16 f! e d } >>
}
}

rhData = \relative {
| f''8 d g
| a,8 fis16 g b g'
| g8 c, e
| g8 d4\trill
| \rhMeasureEight
| g,8 c e
| e16 c e g c g
| c,4 r8
| <c e>8 r8
| b16 a b c d b
| e16 c b a g fis
| <e c'>8 8 8
| c'8( g e)
| c'4 r8
| e8 g16 e c8
| a'8( fis d)
| c16 g c e g, c
| g8( c e)
| e16 c e8 g
| g8 b16 d d,8
| c16 e g d a fis'
| e8 c g
| f'16 e d e f g
| \rhMeasureEight
| d,16 fis a d fis a
| <c, e>8 8 8
| f16 e f d c b
| fis'16 d a a' fis d
| b16 d g d b8
| \rhMeasureEight
| e16[ c g8] e'
| g,8 c e
| \rhMeasureEight
| e16 c d b g8
| a8 d fis
| a,16 e' d g fis a
| g16 b g d b8
| c8 g e'
| g8 g, g
| c16 b c e g, c
| c16 b c e g,8
| b16 c d b a g
| g'8 f16 e d c
| a8 f'16 d a b
| c16 b c g e c
| g''8 b16 g d b
| g'8 g16 d b'8
| e,8 c16 e g c
| e,8( c g)
| c8 e16 c g8
| c16 g e' c g' e
| d16( cis) d f g, b
| <c e>8 16 <d f> <e g>8
| <e, c'>8 8 8
| g'8 b d,
| d16 b g8 r8
| e'8 c g
| g'8 e c
| g'8 c, e
| g8 f16 e d c
| c8 e16 c g'8
| e16 c b g a fis
| e'16 c b c g8
| e'16 g c g e c
| d16 a d8 fis
| fis8 a fis
| c16 b c e g, c
| g'8 b16 g d g
| g8( e c)
| fis8 a16 fis d fis
| g16 b d b g8
| f16 e d c b d
| g8 e c
| c'16 b c g e c
| <d fis>8 8 8
| c'16 b c g e c
| g'16 b g8 d
| c8 c, r
| c'4 r8
| d8 a\turn fis'
| \rhMeasureEight
| d16[ b g8] g'
| c,4 r8
| c16 g e' c g' e
| c8 e g,
| d'8 d16 g b8
| g8 c, e
| g16 d g b g d
| f16 e d8 g
| fis16 a d a fis a
| \rhMeasureEight
| <b, d>8 g'16 b d,8
| c4 r8
| \rhMeasureEight
| g'8 e c
| e8 c g
| g'16 fis g d b g
| c8 g e'
| fis8 a d,
| \rhMeasureEight
| e16 d e g c g
| fis16 d a8 fis'
| c16 e c g e8
| e'16 d e g c g
| fis8 a16 fis d fis
| a,8 d16 c b a
| \rhMeasureEight
| e'8( g c)
| d,16 f d f b, d
| 16( <a c>) q( <g b>) q( <fis a>)
| c'4 r8
| e8 c g
| f'8 d b
| 8 q q
| c16 g e' c g' e
| d16 f a f d b
| d16 a d fis a fis
| e16 a g b fis a
| e16 c g' e c' g
| d'8 a16 fis d a
| g'8 b16 g d8
| g16 fis g b d,8
| \rhMeasureEight
| <e, c'>8 8 8
| g'16 e d b g8
| c16 g c e g <c, e>
| \rhMeasureEight
| b8 d g
| a16 g fis g d8
| <e, c'>8 8 8
| c'4 r8
| <c e>8 16 <g b> g8
| d'8 g16 d b d
| a16 e' <a c> <g b> <fis a>
| fis'8 fis16 d a'8
| c16 b c g e c
| c8 g e'
| <a, d fis>8 fis'4\trill
| g16 b g b d,8
| a8 a16 d fis8
| d16 e f d c b
| c8 g e'
| g8 d16 b g8
| g'8 c, e
| d16 f a, d b d
| <fis, d'>8 <d' fis> <fis a>
| e16 c' b g a fis
| c'16 b c g e c
| f16 d a8 b
| <g c e>8 e'4\trill
| c4 r8
| g'8 f16 e d c
| d16 a fis' d a' fis
| d16 cis d fis a fis
| g16 b g d b g
| c16 g e' c g'8
| e16 d e g c g
| b,8 d16 b a g
| e'16 g d c b a
| c16 b c e g, c
| <fis, d'>8 8 8
| e'16 d e g c g
| g16 fis g d b g
| d'8 g,4
| d'8( b g)
| d'16 b' g d b8
| c8 c16 d e8
| g8 f16 e d c
| e16 g d g a, fis'
| c4 r8
| b16 c d e f d
| c4 r8
| f16 a a,8 b16 d
| g,8 c e
| e16 c b d g8
| a16 g b g d g
}

lhData = \relative {
| f8 d g
| <b, g'>4 r8
| <c e>4 r8
| g16 b g'8 b,
| \lhMeasureEight
| <c e>4 r8
| <c g'>4 r8
| c8 g c,
| g''4 g,8
| g'4 r8
| c,8 d d,
| c'8 8 8
| <e g>4 8
| c8 g c,
| <c' g'>4 <c e>8
| <d fis>4 <c fis>8
| <e g>4 r8
| <c e>4 <c g'>8
| <c g'>4 <c e>8
| b4 r8
| c8 d d,
| c'4 r8
| f16 e d e f g
| \lhMeasureEight
| d4 c8
| c16 e g e c' c,
| <g' b>4 r8
| <c, a'>4 r8
| g'4 g,8
| \lhMeasureEight
| <c g'>4 8
| <c e>4 r8
| \lhMeasureEight
| g'4 r8
| <d fis>4 <c a'>8
| c8 d d,
| <b' d>4 r8
| <c e>16 g' q g q g
| b,16 d g d b g
| <c e>4 r8
| <c e>4 r8
| g4 r8
| <c e>4 r8
| f4 g8
| <e g>4 r8
| 4 r8
| q4 r8
| <c g'>4 <c e>8
| <c e>16 g' q g q g
| <e g>4 r8
| <c e>4 r8
| f4 g8
| c,4 r8
| c8 8 8
| 4 r8
| <g g'>4 g'8
| <c, e>16 g' q g q g
| q16 g q g q g
| q16 g q g q g
| <c, e>4 r8
| <e g>4 r8
| c8 d d,
| c'4 r8
| <c g'>4 8
| <d fis>4 r8
| << { a'8 fis d } \\ { d8 d c } >>
| <c e>4 <e g>8
| b4 r8
| <c e>4 r8
| d4 c8
| 4 8
| f'4 g8
| <c, e>16 g' q g q g
| <c, e>4 r8
| c8 8 8
| <c e>4 <c g'>8
| 4 8
| c4 c,8
| c'8 g c,
| c'4 r8
| \lhMeasureEight
| 4 8
| c8 g c,
| <c' e>4 r8
| <e g>4 r8
| 4 r8
| <c e>4 <c g'>8
| 4 8
| f'16 e d8 g
| <c, a'>4 8
| \lhMeasureEight
| <g g'>4 g'8
| c,8 g c,
| \lhMeasureEight
| <c' e>4 r8
| c4 r8
| 4 8
| <c e>16 g' q g q g
| <c, a'>4 8
| \lhMeasureEight
| <c g'>4 <c e>8
| <c a'>4 8
| <e g>4 r8
| c4 r8
| c4 r8
| c8 d d,
| \lhMeasureEight
| <c' g'>4 <c e>8
| <f a>4 <g d'>8
| c,8 d d,
| c'8 g c,
| <c' e>16 g' q g q g
| <g b>4 r8
| g8 8 8
| <c, e>4 r8
| f4 g8
| <d fis>4 r8
| c8 d d,
| <c' e>4 r8
| <d fis>4 <c fis>8
| 4 r8
| 8 8 
| \lhMeasureEight
| c8 8 8
| g'8 g, r
| e'4 e16 c
| \lhMeasureEight
| g4 r8
| 8 8 
| c8 8 8
| c8 g c,
| g''8 g, r8
| 4 r8
| c8 d d,
| << { d'8 d d } \\ { c8 c c } >>
| << e4 \\ c4 >> r8
| <c e>16 g' q g q g
| d,16 d' cis d c d
| b4 r8
| <c fis>8 8 <c a'>
| 4 g8
| <c e>4 r8
| 4 8
| <c e>16 g' q g q g
| f4 g8
| c,8 8 8
| c8 d d,
| <c' e>4 r8
| f4 g8
| c,16 b c d e fis
| c8 g c,
| <c' e>4 r8
| c4 r8
| c4 r8
| 4 r8
| <e g>4 r8
| c4 r8
| g4 r8
| c8 d d,
| <c' e>4 8
| c8 8 8
| <c g'>4 <c e>8
| 4 r8
| g'16 fis g d b g
| b4 r8
| <g' b>4 r8
| <c, e>4 r8
| <c e>4 <e g>8
| c8 d d,
| c'8 g c,
| <g' g'>4 8
| c8 g c,
| f'4 g8
| <c, e>16 g' q g q g
| g8 g, r8
| 4 8
}

table = #'(
#(96 32 69 40 148 104 152 119 98 3 54)
#(22 6 95 17 74 157 60 84 142 87 130)
#(141 128 158 113 163 27 171 114 42 165 10)
#(41 63 13 85 45 167 53 50 156 61 103)
#(105 146 153 161 80 154 99 140 75 135 28)
#(122 46 55 2 97 68 133 86 129 47 37)
#(11 134 110 159 36 118 21 169 62 147 106)
#(30 81 24 100 107 91 127 94 123 33 5)
#(70 117 66 90 25 138 16 120 65 102 35)
#(121 39 139 176 143 71 155 88 77 4 20)
#(26 126 15 7 64 150 57 48 19 31 108)
#(9 56 132 34 125 29 175 166 82 164 92)
#(112 174 73 67 76 101 43 51 137 144 12)
#(49 18 58 160 136 162 168 115 38 59 124)
#(109 116 145 52 1 23 89 72 149 173 44)
#(14 83 79 170 93 151 172 111 8 78 131)
)

#(define choices
(map (lambda (possibilities)
(1- (vector-ref possibilities (random 11))))
table))

#(define (split-measures music)
(let ((elements (ly:music-property
(ly:music-property music 'element)
'elements)))
(let loop ((elts (reverse elements))
(measure '())
(measures '()))
(cond
((null? elts)
(list->vector measures))
((music-is-of-type? (car elts) 'bar-check)
(let ((measure-music (make-sequential-music measure)))
(loop (cdr elts) '() (cons measure-music measures))))
(else
(loop (cdr elts) (cons (car elts) measure) measures))))))

applyChoices =
#(define-music-function (music) (ly:music?)
(let* ((measures (split-measures music))
(chosen-measures
(map (lambda (i) (vector-ref measures i))
choices))
(first-part (make-sequential-music (take chosen-measures 8)))
(second-part (make-sequential-music (drop chosen-measures 8))))
#{
\repeat volta 2 { #first-part }
\repeat volta 2 { #second-part }
#}))

\header {
title = "Valse"
composer = "Mozart"
}

randomWaltz =
\keepWithTag generation
\new PianoStaff <<
\new Staff {
\time 3/8
\applyChoices \rhData
}
\new Staff {
\clef bass
\applyChoices \lhData
}
>>

\score {
\layout { }
\randomWaltz
}

\score {
\midi { }
\unfoldRepeats \randomWaltz
}

% Uncomment to display the table of all possible measures ("Notentafel")
%{
\score {
\layout {
\context {
\Score
barNumberVisibility = #all-bar-numbers-visible
\override BarNumber.break-visibility = #end-of-line-invisible
centerBarNumbers = ##t
}
}
\keepWithTag table <<
\new Staff {
\time 3/8
\rhData
}
\new Staff {
\clef bass
\lhData
}
>>
}
%}
</lilypond>

Mozart’s Musikalisches Würfelspiel

2026-01-07T15:24:23Z

Jean Abou Samra: Fix volte being swapped around, thanks Werner

Mozart's [https://en.wikipedia.org/wiki/Musikalisches_W%C3%BCrfelspiel Musikalisches Würfelspiel] (score [https://imslp.org/wiki/Musikalisches_W%C3%BCrfelspiel,_K.516f_(Mozart,_Wolfgang_Amadeus) available on IMSLP]) is a system to create a waltz by choosing each measure from a list of possibilities, with 759,499,667,166,482 possible waltzes in total. This is an implementation of the Würfelspiel using a bit of Scheme code to select the measures at random, producing a different waltz at each compilation. The code is an instructive example of creating music functions and manipulating music in Scheme.

<lilypond version="2.24">
rhMeasureEight = \relative {
\tag generation \alternative {
\volta 1 { <g' b d g>4 r8 }
\volta 2 { <g b d g>4 r8 }
}
\tag table {
<g b d g>4 r8
}
}

lhMeasureEight = \relative {
\tag generation \alternative {
\volta 1 { g,8 g'16 f! e d }
\volta 2 { g,8 b'16 g fis e }
}
\tag table {
<< { g,8_"Volta 1" g'16 f! e d } \\ { g,8^"Volta 2" b'16 g fis e } >>
}
}

rhData = \relative {
| f''8 d g
| a,8 fis16 g b g'
| g8 c, e
| g8 d4\trill
| \rhMeasureEight
| g,8 c e
| e16 c e g c g
| c,4 r8
| <c e>8 r8
| b16 a b c d b
| e16 c b a g fis
| <e c'>8 8 8
| c'8( g e)
| c'4 r8
| e8 g16 e c8
| a'8( fis d)
| c16 g c e g, c
| g8( c e)
| e16 c e8 g
| g8 b16 d d,8
| c16 e g d a fis'
| e8 c g
| f'16 e d e f g
| \rhMeasureEight
| d,16 fis a d fis a
| <c, e>8 8 8
| f16 e f d c b
| fis'16 d a a' fis d
| b16 d g d b8
| \rhMeasureEight
| e16[ c g8] e'
| g,8 c e
| \rhMeasureEight
| e16 c d b g8
| a8 d fis
| a,16 e' d g fis a
| g16 b g d b8
| c8 g e'
| g8 g, g
| c16 b c e g, c
| c16 b c e g,8
| b16 c d b a g
| g'8 f16 e d c
| a8 f'16 d a b
| c16 b c g e c
| g''8 b16 g d b
| g'8 g16 d b'8
| e,8 c16 e g c
| e,8( c g)
| c8 e16 c g8
| c16 g e' c g' e
| d16( cis) d f g, b
| <c e>8 16 <d f> <e g>8
| <e, c'>8 8 8
| g'8 b d,
| d16 b g8 r8
| e'8 c g
| g'8 e c
| g'8 c, e
| g8 f16 e d c
| c8 e16 c g'8
| e16 c b g a fis
| e'16 c b c g8
| e'16 g c g e c
| d16 a d8 fis
| fis8 a fis
| c16 b c e g, c
| g'8 b16 g d g
| g8( e c)
| fis8 a16 fis d fis
| g16 b d b g8
| f16 e d c b d
| g8 e c
| c'16 b c g e c
| <d fis>8 8 8
| c'16 b c g e c
| g'16 b g8 d
| c8 c, r
| c'4 r8
| d8 a\turn fis'
| \rhMeasureEight
| d16[ b g8] g'
| c,4 r8
| c16 g e' c g' e
| c8 e g,
| d'8 d16 g b8
| g8 c, e
| g16 d g b g d
| f16 e d8 g
| fis16 a d a fis a
| \rhMeasureEight
| <b, d>8 g'16 b d,8
| c4 r8
| \rhMeasureEight
| g'8 e c
| e8 c g
| g'16 fis g d b g
| c8 g e'
| fis8 a d,
| \rhMeasureEight
| e16 d e g c g
| fis16 d a8 fis'
| c16 e c g e8
| e'16 d e g c g
| fis8 a16 fis d fis
| a,8 d16 c b a
| \rhMeasureEight
| e'8( g c)
| d,16 f d f b, d
| 16( <a c>) q( <g b>) q( <fis a>)
| c'4 r8
| e8 c g
| f'8 d b
| 8 q q
| c16 g e' c g' e
| d16 f a f d b
| d16 a d fis a fis
| e16 a g b fis a
| e16 c g' e c' g
| d'8 a16 fis d a
| g'8 b16 g d8
| g16 fis g b d,8
| \rhMeasureEight
| <e, c'>8 8 8
| g'16 e d b g8
| c16 g c e g <c, e>
| \rhMeasureEight
| b8 d g
| a16 g fis g d8
| <e, c'>8 8 8
| c'4 r8
| <c e>8 16 <g b> g8
| d'8 g16 d b d
| a16 e' <a c> <g b> <fis a>
| fis'8 fis16 d a'8
| c16 b c g e c
| c8 g e'
| <a, d fis>8 fis'4\trill
| g16 b g b d,8
| a8 a16 d fis8
| d16 e f d c b
| c8 g e'
| g8 d16 b g8
| g'8 c, e
| d16 f a, d b d
| <fis, d'>8 <d' fis> <fis a>
| e16 c' b g a fis
| c'16 b c g e c
| f16 d a8 b
| <g c e>8 e'4\trill
| c4 r8
| g'8 f16 e d c
| d16 a fis' d a' fis
| d16 cis d fis a fis
| g16 b g d b g
| c16 g e' c g'8
| e16 d e g c g
| b,8 d16 b a g
| e'16 g d c b a
| c16 b c e g, c
| <fis, d'>8 8 8
| e'16 d e g c g
| g16 fis g d b g
| d'8 g,4
| d'8( b g)
| d'16 b' g d b8
| c8 c16 d e8
| g8 f16 e d c
| e16 g d g a, fis'
| c4 r8
| b16 c d e f d
| c4 r8
| f16 a a,8 b16 d
| g,8 c e
| e16 c b d g8
| a16 g b g d g
}

lhData = \relative {
| f8 d g
| <b, g'>4 r8
| <c e>4 r8
| g16 b g'8 b,
| \lhMeasureEight
| <c e>4 r8
| <c g'>4 r8
| c8 g c,
| g''4 g,8
| g'4 r8
| c,8 d d,
| c'8 8 8
| <e g>4 8
| c8 g c,
| <c' g'>4 <c e>8
| <d fis>4 <c fis>8
| <e g>4 r8
| <c e>4 <c g'>8
| <c g'>4 <c e>8
| b4 r8
| c8 d d,
| c'4 r8
| f16 e d e f g
| \lhMeasureEight
| d4 c8
| c16 e g e c' c,
| <g' b>4 r8
| <c, a'>4 r8
| g'4 g,8
| \lhMeasureEight
| <c g'>4 8
| <c e>4 r8
| \lhMeasureEight
| g'4 r8
| <d fis>4 <c a'>8
| c8 d d,
| <b' d>4 r8
| <c e>16 g' q g q g
| b,16 d g d b g
| <c e>4 r8
| <c e>4 r8
| g4 r8
| <c e>4 r8
| f4 g8
| <e g>4 r8
| 4 r8
| q4 r8
| <c g'>4 <c e>8
| <c e>16 g' q g q g
| <e g>4 r8
| <c e>4 r8
| f4 g8
| c,4 r8
| c8 8 8
| 4 r8
| <g g'>4 g'8
| <c, e>16 g' q g q g
| q16 g q g q g
| q16 g q g q g
| <c, e>4 r8
| <e g>4 r8
| c8 d d,
| c'4 r8
| <c g'>4 8
| <d fis>4 r8
| << { a'8 fis d } \\ { d8 d c } >>
| <c e>4 <e g>8
| b4 r8
| <c e>4 r8
| d4 c8
| 4 8
| f'4 g8
| <c, e>16 g' q g q g
| <c, e>4 r8
| c8 8 8
| <c e>4 <c g'>8
| 4 8
| c4 c,8
| c'8 g c,
| c'4 r8
| \lhMeasureEight
| 4 8
| c8 g c,
| <c' e>4 r8
| <e g>4 r8
| 4 r8
| <c e>4 <c g'>8
| 4 8
| f'16 e d8 g
| <c, a'>4 8
| \lhMeasureEight
| <g g'>4 g'8
| c,8 g c,
| \lhMeasureEight
| <c' e>4 r8
| c4 r8
| 4 8
| <c e>16 g' q g q g
| <c, a'>4 8
| \lhMeasureEight
| <c g'>4 <c e>8
| <c a'>4 8
| <e g>4 r8
| c4 r8
| c4 r8
| c8 d d,
| \lhMeasureEight
| <c' g'>4 <c e>8
| <f a>4 <g d'>8
| c,8 d d,
| c'8 g c,
| <c' e>16 g' q g q g
| <g b>4 r8
| g8 8 8
| <c, e>4 r8
| f4 g8
| <d fis>4 r8
| c8 d d,
| <c' e>4 r8
| <d fis>4 <c fis>8
| 4 r8
| 8 8 
| \lhMeasureEight
| c8 8 8
| g'8 g, r
| e'4 e16 c
| \lhMeasureEight
| g4 r8
| 8 8 
| c8 8 8
| c8 g c,
| g''8 g, r8
| 4 r8
| c8 d d,
| << { d'8 d d } \\ { c8 c c } >>
| << e4 \\ c4 >> r8
| <c e>16 g' q g q g
| d,16 d' cis d c d
| b4 r8
| <c fis>8 8 <c a'>
| 4 g8
| <c e>4 r8
| 4 8
| <c e>16 g' q g q g
| f4 g8
| c,8 8 8
| c8 d d,
| <c' e>4 r8
| f4 g8
| c,16 b c d e fis
| c8 g c,
| <c' e>4 r8
| c4 r8
| c4 r8
| 4 r8
| <e g>4 r8
| c4 r8
| g4 r8
| c8 d d,
| <c' e>4 8
| c8 8 8
| <c g'>4 <c e>8
| 4 r8
| g'16 fis g d b g
| b4 r8
| <g' b>4 r8
| <c, e>4 r8
| <c e>4 <e g>8
| c8 d d,
| c'8 g c,
| <g' g'>4 8
| c8 g c,
| f'4 g8
| <c, e>16 g' q g q g
| g8 g, r8
| 4 8
}

table = #'(
#(96 32 69 40 148 104 152 119 98 3 54)
#(22 6 95 17 74 157 60 84 142 87 130)
#(141 128 158 113 163 27 171 114 42 165 10)
#(41 63 13 85 45 167 53 50 156 61 103)
#(105 146 153 161 80 154 99 140 75 135 28)
#(122 46 55 2 97 68 133 86 129 47 37)
#(11 134 110 159 36 118 21 169 62 147 106)
#(30 81 24 100 107 91 127 94 123 33 5)
#(70 117 66 90 25 138 16 120 65 102 35)
#(121 39 139 176 143 71 155 88 77 4 20)
#(26 126 15 7 64 150 57 48 19 31 108)
#(9 56 132 34 125 29 175 166 82 164 92)
#(112 174 73 67 76 101 43 51 137 144 12)
#(49 18 58 160 136 162 168 115 38 59 124)
#(109 116 145 52 1 23 89 72 149 173 44)
#(14 83 79 170 93 151 172 111 8 78 131)
)

#(define choices
(map (lambda (possibilities)
(1- (vector-ref possibilities (random 11))))
table))

#(define (split-measures music)
(let ((elements (ly:music-property
(ly:music-property music 'element)
'elements)))
(let loop ((elts (reverse elements))
(measure '())
(measures '()))
(cond
((null? elts)
(list->vector measures))
((music-is-of-type? (car elts) 'bar-check)
(let ((measure-music (make-sequential-music measure)))
(loop (cdr elts) '() (cons measure-music measures))))
(else
(loop (cdr elts) (cons (car elts) measure) measures))))))

applyChoices =
#(define-music-function (music) (ly:music?)
(let* ((measures (split-measures music))
(chosen-measures
(map (lambda (i) (vector-ref measures i))
choices))
(first-part (make-sequential-music (take chosen-measures 8)))
(second-part (make-sequential-music (drop chosen-measures 8))))
#{
\repeat volta 2 { #first-part }
\repeat volta 2 { #second-part }
#}))

\header {
title = "Valse"
composer = "Mozart"
}

randomWaltz =
\keepWithTag generation
\new PianoStaff <<
\new Staff {
\time 3/8
\applyChoices \rhData
}
\new Staff {
\clef bass
\applyChoices \lhData
}
>>

\score {
\layout { }
\randomWaltz
}

\score {
\midi { }
\unfoldRepeats \randomWaltz
}

% Uncomment to display the table of all possible measures ("Notentafel")
%{
\score {
\layout {
\context {
\Score
barNumberVisibility = #all-bar-numbers-visible
\override BarNumber.break-visibility = #end-of-line-invisible
centerBarNumbers = ##t
}
}
\keepWithTag table <<
\new Staff {
\time 3/8
\rhData
}
\new Staff {
\clef bass
\lhData
}
>>
}
%}
</lilypond>

Mozart’s Musikalisches Würfelspiel

2026-01-07T14:46:38Z

Jean Abou Samra: Create

Mozart's [https://en.wikipedia.org/wiki/Musikalisches_W%C3%BCrfelspiel Musikalisches Würfelspiel] (score [https://imslp.org/wiki/Musikalisches_W%C3%BCrfelspiel,_K.516f_(Mozart,_Wolfgang_Amadeus) available on IMSLP]) is a system to create a waltz by choosing each measure from a list of possibilities, with 759,499,667,166,482 possible waltzes in total. This is an implementation of the Würfelspiel using a bit of Scheme code to select the measures at random, producing a different waltz at each compilation. The code is an instructive example of creating music functions and manipulating music in Scheme.

<lilypond version="2.24">
rhMeasureEight = \relative {
\tag generation \alternative {
\volta 1 { <g' b d g>4 r8 }
\volta 2 { <g b d g>4 r8 }
}
\tag table {
<g b d g>4 r8
}
}

lhMeasureEight = \relative {
\tag generation \alternative {
\volta 1 { g,8 b'16 g fis e }
\volta 2 { g,8 g'16 f! e d }
}
\tag table {
<< { g,8^"Volta 1" b'16 g fis e } \\ { g,8_"Volta 2" g'16 f! e d } >>
}
}

rhData = \relative {
| f''8 d g
| a,8 fis16 g b g'
| g8 c, e
| g8 d4\trill
| \rhMeasureEight
| g,8 c e
| e16 c e g c g
| c,4 r8
| <c e>8 r8
| b16 a b c d b
| e16 c b a g fis
| <e c'>8 8 8
| c'8( g e)
| c'4 r8
| e8 g16 e c8
| a'8( fis d)
| c16 g c e g, c
| g8( c e)
| e16 c e8 g
| g8 b16 d d,8
| c16 e g d a fis'
| e8 c g
| f'16 e d e f g
| \rhMeasureEight
| d,16 fis a d fis a
| <c, e>8 8 8
| f16 e f d c b
| fis'16 d a a' fis d
| b16 d g d b8
| \rhMeasureEight
| e16[ c g8] e'
| g,8 c e
| \rhMeasureEight
| e16 c d b g8
| a8 d fis
| a,16 e' d g fis a
| g16 b g d b8
| c8 g e'
| g8 g, g
| c16 b c e g, c
| c16 b c e g,8
| b16 c d b a g
| g'8 f16 e d c
| a8 f'16 d a b
| c16 b c g e c
| g''8 b16 g d b
| g'8 g16 d b'8
| e,8 c16 e g c
| e,8( c g)
| c8 e16 c g8
| c16 g e' c g' e
| d16( cis) d f g, b
| <c e>8 16 <d f> <e g>8
| <e, c'>8 8 8
| g'8 b d,
| d16 b g8 r8
| e'8 c g
| g'8 e c
| g'8 c, e
| g8 f16 e d c
| c8 e16 c g'8
| e16 c b g a fis
| e'16 c b c g8
| e'16 g c g e c
| d16 a d8 fis
| fis8 a fis
| c16 b c e g, c
| g'8 b16 g d g
| g8( e c)
| fis8 a16 fis d fis
| g16 b d b g8
| f16 e d c b d
| g8 e c
| c'16 b c g e c
| <d fis>8 8 8
| c'16 b c g e c
| g'16 b g8 d
| c8 c, r
| c'4 r8
| d8 a\turn fis'
| \rhMeasureEight
| d16[ b g8] g'
| c,4 r8
| c16 g e' c g' e
| c8 e g,
| d'8 d16 g b8
| g8 c, e
| g16 d g b g d
| f16 e d8 g
| fis16 a d a fis a
| \rhMeasureEight
| <b, d>8 g'16 b d,8
| c4 r8
| \rhMeasureEight
| g'8 e c
| e8 c g
| g'16 fis g d b g
| c8 g e'
| fis8 a d,
| \rhMeasureEight
| e16 d e g c g
| fis16 d a8 fis'
| c16 e c g e8
| e'16 d e g c g
| fis8 a16 fis d fis
| a,8 d16 c b a
| \rhMeasureEight
| e'8( g c)
| d,16 f d f b, d
| 16( <a c>) q( <g b>) q( <fis a>)
| c'4 r8
| e8 c g
| f'8 d b
| 8 q q
| c16 g e' c g' e
| d16 f a f d b
| d16 a d fis a fis
| e16 a g b fis a
| e16 c g' e c' g
| d'8 a16 fis d a
| g'8 b16 g d8
| g16 fis g b d,8
| \rhMeasureEight
| <e, c'>8 8 8
| g'16 e d b g8
| c16 g c e g <c, e>
| \rhMeasureEight
| b8 d g
| a16 g fis g d8
| <e, c'>8 8 8
| c'4 r8
| <c e>8 16 <g b> g8
| d'8 g16 d b d
| a16 e' <a c> <g b> <fis a>
| fis'8 fis16 d a'8
| c16 b c g e c
| c8 g e'
| <a, d fis>8 fis'4\trill
| g16 b g b d,8
| a8 a16 d fis8
| d16 e f d c b
| c8 g e'
| g8 d16 b g8
| g'8 c, e
| d16 f a, d b d
| <fis, d'>8 <d' fis> <fis a>
| e16 c' b g a fis
| c'16 b c g e c
| f16 d a8 b
| <g c e>8 e'4\trill
| c4 r8
| g'8 f16 e d c
| d16 a fis' d a' fis
| d16 cis d fis a fis
| g16 b g d b g
| c16 g e' c g'8
| e16 d e g c g
| b,8 d16 b a g
| e'16 g d c b a
| c16 b c e g, c
| <fis, d'>8 8 8
| e'16 d e g c g
| g16 fis g d b g
| d'8 g,4
| d'8( b g)
| d'16 b' g d b8
| c8 c16 d e8
| g8 f16 e d c
| e16 g d g a, fis'
| c4 r8
| b16 c d e f d
| c4 r8
| f16 a a,8 b16 d
| g,8 c e
| e16 c b d g8
| a16 g b g d g
}

lhData = \relative {
| f8 d g
| <b, g'>4 r8
| <c e>4 r8
| g16 b g'8 b,
| \lhMeasureEight
| <c e>4 r8
| <c g'>4 r8
| c8 g c,
| g''4 g,8
| g'4 r8
| c,8 d d,
| c'8 8 8
| <e g>4 8
| c8 g c,
| <c' g'>4 <c e>8
| <d fis>4 <c fis>8
| <e g>4 r8
| <c e>4 <c g'>8
| <c g'>4 <c e>8
| b4 r8
| c8 d d,
| c'4 r8
| f16 e d e f g
| \lhMeasureEight
| d4 c8
| c16 e g e c' c,
| <g' b>4 r8
| <c, a'>4 r8
| g'4 g,8
| \lhMeasureEight
| <c g'>4 8
| <c e>4 r8
| \lhMeasureEight
| g'4 r8
| <d fis>4 <c a'>8
| c8 d d,
| <b' d>4 r8
| <c e>16 g' q g q g
| b,16 d g d b g
| <c e>4 r8
| <c e>4 r8
| g4 r8
| <c e>4 r8
| f4 g8
| <e g>4 r8
| 4 r8
| q4 r8
| <c g'>4 <c e>8
| <c e>16 g' q g q g
| <e g>4 r8
| <c e>4 r8
| f4 g8
| c,4 r8
| c8 8 8
| 4 r8
| <g g'>4 g'8
| <c, e>16 g' q g q g
| q16 g q g q g
| q16 g q g q g
| <c, e>4 r8
| <e g>4 r8
| c8 d d,
| c'4 r8
| <c g'>4 8
| <d fis>4 r8
| << { a'8 fis d } \\ { d8 d c } >>
| <c e>4 <e g>8
| b4 r8
| <c e>4 r8
| d4 c8
| 4 8
| f'4 g8
| <c, e>16 g' q g q g
| <c, e>4 r8
| c8 8 8
| <c e>4 <c g'>8
| 4 8
| c4 c,8
| c'8 g c,
| c'4 r8
| \lhMeasureEight
| 4 8
| c8 g c,
| <c' e>4 r8
| <e g>4 r8
| 4 r8
| <c e>4 <c g'>8
| 4 8
| f'16 e d8 g
| <c, a'>4 8
| \lhMeasureEight
| <g g'>4 g'8
| c,8 g c,
| \lhMeasureEight
| <c' e>4 r8
| c4 r8
| 4 8
| <c e>16 g' q g q g
| <c, a'>4 8
| \lhMeasureEight
| <c g'>4 <c e>8
| <c a'>4 8
| <e g>4 r8
| c4 r8
| c4 r8
| c8 d d,
| \lhMeasureEight
| <c' g'>4 <c e>8
| <f a>4 <g d'>8
| c,8 d d,
| c'8 g c,
| <c' e>16 g' q g q g
| <g b>4 r8
| g8 8 8
| <c, e>4 r8
| f4 g8
| <d fis>4 r8
| c8 d d,
| <c' e>4 r8
| <d fis>4 <c fis>8
| 4 r8
| 8 8 
| \lhMeasureEight
| c8 8 8
| g'8 g, r
| e'4 e16 c
| \lhMeasureEight
| g4 r8
| 8 8 
| c8 8 8
| c8 g c,
| g''8 g, r8
| 4 r8
| c8 d d,
| << { d'8 d d } \\ { c8 c c } >>
| << e4 \\ c4 >> r8
| <c e>16 g' q g q g
| d,16 d' cis d c d
| b4 r8
| <c fis>8 8 <c a'>
| 4 g8
| <c e>4 r8
| 4 8
| <c e>16 g' q g q g
| f4 g8
| c,8 8 8
| c8 d d,
| <c' e>4 r8
| f4 g8
| c,16 b c d e fis
| c8 g c,
| <c' e>4 r8
| c4 r8
| c4 r8
| 4 r8
| <e g>4 r8
| c4 r8
| g4 r8
| c8 d d,
| <c' e>4 8
| c8 8 8
| <c g'>4 <c e>8
| 4 r8
| g'16 fis g d b g
| b4 r8
| <g' b>4 r8
| <c, e>4 r8
| <c e>4 <e g>8
| c8 d d,
| c'8 g c,
| <g' g'>4 8
| c8 g c,
| f'4 g8
| <c, e>16 g' q g q g
| g8 g, r8
| 4 8
}

table = #'(
#(96 32 69 40 148 104 152 119 98 3 54)
#(22 6 95 17 74 157 60 84 142 87 130)
#(141 128 158 113 163 27 171 114 42 165 10)
#(41 63 13 85 45 167 53 50 156 61 103)
#(105 146 153 161 80 154 99 140 75 135 28)
#(122 46 55 2 97 68 133 86 129 47 37)
#(11 134 110 159 36 118 21 169 62 147 106)
#(30 81 24 100 107 91 127 94 123 33 5)
#(70 117 66 90 25 138 16 120 65 102 35)
#(121 39 139 176 143 71 155 88 77 4 20)
#(26 126 15 7 64 150 57 48 19 31 108)
#(9 56 132 34 125 29 175 166 82 164 92)
#(112 174 73 67 76 101 43 51 137 144 12)
#(49 18 58 160 136 162 168 115 38 59 124)
#(109 116 145 52 1 23 89 72 149 173 44)
#(14 83 79 170 93 151 172 111 8 78 131)
)

#(define choices
(map (lambda (possibilities)
(1- (vector-ref possibilities (random 11))))
table))

#(define (split-measures music)
(let ((elements (ly:music-property
(ly:music-property music 'element)
'elements)))
(let loop ((elts (reverse elements))
(measure '())
(measures '()))
(cond
((null? elts)
(list->vector measures))
((music-is-of-type? (car elts) 'bar-check)
(let ((measure-music (make-sequential-music measure)))
(loop (cdr elts) '() (cons measure-music measures))))
(else
(loop (cdr elts) (cons (car elts) measure) measures))))))

applyChoices =
#(define-music-function (music) (ly:music?)
(let* ((measures (split-measures music))
(chosen-measures
(map (lambda (i) (vector-ref measures i))
choices))
(first-part (make-sequential-music (take chosen-measures 8)))
(second-part (make-sequential-music (drop chosen-measures 8))))
#{
\repeat volta 2 { #first-part }
\repeat volta 2 { #second-part }
#}))

\header {
title = "Valse"
composer = "Mozart"
}

randomWaltz =
\keepWithTag generation
\new PianoStaff <<
\new Staff {
\time 3/8
\applyChoices \rhData
}
\new Staff {
\clef bass
\applyChoices \lhData
}
>>

\score {
\layout { }
\randomWaltz
}

\score {
\midi { }
\unfoldRepeats \randomWaltz
}

% Uncomment to display the table of all possible measures ("Notentafel")
%{
\score {
\layout {
\context {
\Score
barNumberVisibility = #all-bar-numbers-visible
\override BarNumber.break-visibility = #end-of-line-invisible
centerBarNumbers = ##t
}
}
\keepWithTag table <<
\new Staff {
\time 3/8
\rhData
}
\new Staff {
\clef bass
\lhData
}
>>
}
%}
</lilypond>

User talk:Jean Abou Samra

2026-01-01T22:02:31Z

Jean Abou Samra: /* This wiki has no templates */ Reply

== Test of email notifications ==

This is a test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 02:46, 2 November 2025 (UTC)

:Another test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:04, 2 November 2025 (UTC)
::Third test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:05, 2 November 2025 (UTC)
:::Reply test. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 03:05, 2 November 2025 (UTC)
::::Yet another test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:14, 2 November 2025 (UTC)

== Default stylesheet for the Wiki ==

Jean,

you've recently removed paper indentation settings from [[Rest styles]], arguing that no indentation is the default for this Wiki. However, this snippet is part of the “official” documentation that doesn't set the indentation to zero by default...

I thus wonder whether it makes sense to synchronize the Wiki with the LilyPond documentation by not providing a default value for the indentation. Another reason to stay with LilyPond's default is that a novice user who tries to compile a snippet might be surprised that it looks differently. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 16:51, 23 November 2025 (UTC)

:I'm surprised. [https://lilypond.org/doc/v2.25/Documentation/contributor/lilypond-formatting This page of the contributor's guide] implies <code>indent = 0</code> is the default in doc snippets. Is it out of date? What are the exact settings used to compile snippets in the docs? It's been too long since I had any idea how the doc build works, I can't find this in the repo right now… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:13, 23 November 2025 (UTC)
::I took the style settings used on the wiki [https://lilypond.org/doc/v2.25/Documentation/usage/other-programs right from the usage manual] in the section that says "you have to effectively mimick how lilypond-book runs lilypond"… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:15, 23 November 2025 (UTC)
:::D'oh. You are correct. My mistake, my memory failed me, and of course I didn't check before writing :-)
:::Sorry for the noise -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:22, 23 November 2025 (UTC)

== cropped SVG images ==

Jean, please have a look at the image in [[Custodes]] – the mensural custodes in the fourth staff are cropped. If you download the SVG image and use a program like `inkview` you can see that the image actually contains the complete glyphs, however, the bounding box is too tight (an old LilyPond issue, as you certainly know).

Is there a possibility to increase the bounding boxes of all images (both horizontally and vertically) using a post-processing step so that cropping can be avoided? -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 10:40, 25 November 2025 (UTC)

:Seems a bit overkill to me. I've added a simple workaround to that snippet. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 12:41, 25 November 2025 (UTC)
::Nice, thanks! I didn't think of this simple fix. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:27, 25 November 2025 (UTC)

== Some CSS code for <nowiki><samp></nowiki> ==

Jean, what do you think of adding something like the following

<pre>
body { quotes: '‘' '’'; }
samp:before { content: open-quote; }
samp:after { content: close-quote; }
</pre>

to the Wiki CSS for the sake of better conversion to Texinfo? My reasoning is as follows.

There is a strong visual difference between <code><nowiki><code></nowiki></code> in the Wiki and <code>@code</code> in Texinfo output: the former produces typewriter text in a box, the latter uses just typewriter. This is fine with the fonts used for Texinfo output except for marking single letters: in Texinfo it is better to use <code>@samp</code> for this situation, producing typewriter text in quotes.

On the Wiki side I would thus like to use <code><nowiki><samp></nowiki></code>, which <code>makelsr.pl</code> converts to <code>@samp</code>. However, it currently produces plain typewriter in the Wiki, which isn't ideal since the contrast to plain text isn't large enough IMHO.

Example: The letter <samp>s</samp> is marked with <code><nowiki><samp></nowiki></code>. My suggestion: The letter ‘<samp>s</samp>’ is marked with <code><nowiki><samp></nowiki></code>.

An alternative would be to give <code><nowiki><samp></nowiki></code> the same appearance as <code><nowiki><code></nowiki></code>. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:15, 30 November 2025 (UTC)

:Done. Thanks for providing the CSS code. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 15:28, 6 December 2025 (UTC)

:: Ah, I missed that with this CSS code the quote characters are also in typewriter, which is not correct. So please add <code>font-family: sans-serif;</code> to both the <code>samp:before</code> and <code>samp:after</code> block.
:: [I haven't found out how to display the quotes with the same font selected by the user to display the main font in Wiki – or is this fixed to always be sans-serif?]

::: Done. I don't know a better solution either. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 14:30, 8 December 2025 (UTC)
:::Thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:48, 9 December 2025 (UTC)

== Search issues ==

Jean,

To get nice snippet headings in the documentation, we often use non-letter stuff like opening and closing quotes in Wiki page titles. However, as I've found out recently, this severely hampers searching. For example, the snippet [[Using \arpeggioBracket to make divisi more visible]] cannot be immediately found by entering “Using arpeggioBracket” (i.e., without the backslash) into the search field.

I now wonder whether the Wiki can be configured to ignore quote characters and the like in the search. If this is not possible, I have to add redirections for all articles with such characters in its name. It's not a big deal since it can be done programmatically, however, not needing this would be a better solution. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:55, 9 December 2025 (UTC)

:AFAIU the autocompletion just matches by title prefix (to be clear, this is not about the search results page you get if you press Enter, which is much more complete). I think it's not too bad, not sure if there's any way to change it. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 14:13, 9 December 2025 (UTC)
::OK, thanks. What do you think of installing the [https://www.mediawiki.org/wiki/Extension:CirrusSearch Cirrus search extension]? It seems that Wikimedia is using this by default, and it comes with fuzzy search support, AFAICS. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 14:47, 9 December 2025 (UTC)
:::It looks like there is no opensearch package in Fedora, and honestly I'm not too keen on setting up a tool as large and complex as MediaWiki itself requiring its own systemd services and networks ports and so on if it's only for the sake of this autocompletion… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:20, 12 December 2025 (UTC)

== More fonts for the Wiki ==

Jean,

please have a look at the snippet [[Changing the default text font family]]: as can be seen, some font shapes for DejaVu Mono are missing. Is it possible to get them added to the server that runs the Wiki?

BTW, the same holds for the [[UTF-8]] snippet, where Japanese is missing.
-- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 15:39, 12 December 2025 (UTC)

:Fixed. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:34, 12 December 2025 (UTC)
::Thanks, but are you sure that the CJK font is working correctly? I tried to modify the [[UTF-8]] snippet to trigger a re-rendering, but I still can't see any Japanese... -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 20:44, 12 December 2025 (UTC)
:::Oops, indeed. But I don't understand why. On the server, <code>-dshow-available-fonts</code> does list "Noto Serif CJK JP". And curiously, if I remove all font settings and compile the code with different versions, it starts working between 2.25.12 and 2.25.13. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 23:49, 12 December 2025 (UTC)
::::Ah, I forgot that Google added Font Variation (VF) versions of the CJK fonts, and the various GNU/Linux distros eagerly took them to make the font bundles much smaller. Older LilyPond versions cannot reject these fonts correctly.
::::For me it works with 2.24.4 if you use the font <code>[https://github.com/notofonts/noto-cjk/blob/main/Serif/OTF/Japanese/NotoSerifCJKjp-Regular.otf NotoSerifCJKjp-Regular.otf]</code> (probably also installing the [https://github.com/notofonts/noto-cjk/blob/main/Serif/OTF/Japanese/NotoSerifCJKjp-Bold.otf bold version] for completeness), and this font is found first. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 04:24, 13 December 2025 (UTC)
:::::Thanks, I've added these fonts on the server as a workaround. The snippet now displays correctly. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 09:13, 13 December 2025 (UTC)
::::::Great, thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 10:50, 13 December 2025 (UTC)

== This wiki has no templates ==

Would it be ok if I created some templates? And I am missing several AddOns, CharInsert would be nice for editing, SyntaxHighlight, Scribunto. I am running a rather private Lilypond Wiki in German for several years and have some experience with Wikis, [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 15:13, 18 December 2025 (UTC)

:Feel free to create all kinds of pages, including templates. However, I'd prefer if they were created as needed for specific pages (i.e., don't create templates "for the future" that aren't used on any pages). Also, I don't see much that could be factored between pages so what's your use case? In particular, please don't create templates similar [[wikipedia:Template:Em|<code><nowiki>{{em|...}}</nowiki></code> on Wikipedia]] that add friction to the editing process for a negligible payoff.
:I haven't installed the extensions you requested because:
:# I don't see any special characters that would be needed particularly often on this wiki specifically, and I'd rather not maintain a general list of special characters, this is the job of system-level input methods like Compose keys and character map apps IMHO.
:# It wouldn't make much sense to have syntax highlighting only for the few code snippets that use <code><nowiki><pre></nowiki></code>, as opposed to <code><nowiki><lilypond></nowiki></code>. However, if someone submits a change for adding syntax highlighting to the output of <code><nowiki><lilypond></nowiki></code> in the [https://gitlab.com/jeanas/LilyWiki extension] that defines this tag for the wiki, I'll be happy to review it.
:# Scribunto has security implications (e.g., the need to keep Lua updated), so I'd rather only install it if there is a compelling use case for that.
:[[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 21:10, 18 December 2025 (UTC)
::Thank you for your answer. You have a point with security issues, SyntaxHighlight needs Scribunto. There is no special language support for Lilypond anyway, I use Latex, better than nothing. Your installation has to offer proc open, otherwise Scribunto is not working. I have not found a single provider which allows this.
::Maybe I am missing something in my preferences, when editing I do not see anything that supports editing, not even the option to insert links, maybe it's because I don't use the visual editor, I like "pure" editing as it is in Lilypond. CharInsert offers support for Wiki syntax, including tags like <pre>, all combinations of {} and so on.
::Greetings from Austria, [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 03:17, 19 December 2025 (UTC)
:::[off-topic] Where in Austria? Greetings from Kufstein :-) -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:15, 19 December 2025 (UTC)
::::Niederösterreich, nordöstlich von Wien (Bezirk Gänserndorf) [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 15:21, 19 December 2025 (UTC)
:::I don't think SyntaxHighlight needs Scribunto. It uses Pygments, which is a Python (not Lua) library (of which I actually am technically a maintainer, although I've been inactive lately by lack of time). It certainly needs something like <code>exec</code>/<code>proc_open</code>, but this wiki doesn't use a "managed" MediaWiki install (where the provider installs things for you, à la "Wordpress in one click"), it's on a VPS on which I have root access and administrate things myself, so I can install and configure anything (and <code>exec</code> is already being used to run LilyPond). The real problem is that the LilyPond code snippets are mostly added through a the special, non-standard parser tag <code><nowiki><lilypond></nowiki></code> and so the extension I wrote that defines this tag would need to support syntax highlighting.
:::Regarding the editor toolbar, it sounds like what you want is not CharInsert but [https://www.mediawiki.org/wiki/Extension:WikiEditor WikiEditor], which I've just added. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:15, 19 December 2025 (UTC)
::::PS: I also meant to write that Pygments supports LilyPond. (I implemented this a few years ago.) [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:26, 19 December 2025 (UTC)
:::::Apropos Pygments: I've submitted a [https://github.com/pygments/pygments/pull/2974 PR] to update LilyPond support some time ago. [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:38, 19 December 2025 (UTC)
::::Thank you for installing this extension, this is definitely an improvement. CharInsert is a different animal. Root access is of course best, but you have to do much administration. Usually root access is very expensive when you need a provider. A long time ago I have written a Lilypond extension myself on a home server in my local network.
::::Just in case you are asking who I am, I wrote LSR 1040, 1042, 1043, 1044 (when I remember right) and was involved in 1066 and 1067. [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 19:34, 19 December 2025 (UTC)
:::::I've discovered a potential reason for activating Scribunto: Right now, I'm using the <code>query</code> MediaWiki API to download snippets for <code>makelsr.pl</code>. However, <code>query</code> doesn't expand templates. This means that I have to call the <code>expandtemplates</code> API, sending the unexpanded page to the Wiki server to get an expanded version back.
:::::The Skribunto interface provides [https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#frame:preprocess <code>frame:preprocess</code>], which seems to unify the abovementioned two calls into a single one (I haven't tested it). Maybe this can be configured to not use Lua, in case this simplifies things. What do you think? -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 14:56, 1 January 2026 (UTC)
::::::I don't see a problem with one extra API call per page to expand templates. Also, the function you link is a Lua API, for use in Lua modules running on the wiki, so I don't get how you want to use it outside. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 22:02, 1 January 2026 (UTC)

== MediaWiki variables for current stable and unstable LilyPond versions ==

Jean,

what do you think about adding [https://www.mediawiki.org/wiki/Manual:Variable MediaWiki variables] that indicate the current stable and unstable LilyPond versions (without the ‘micro’ value)? I suggest

<nowiki>{{LILYSTABLE}}</nowiki> → 2.24
<nowiki>{{LILYDEVEL}}</nowiki> → 2.25

and maybe

<nowiki>{{LILYSTABLEDOC}} → https://lilypond.org/docs/{{LILYSTABLE}}/Documentation</nowiki>
<nowiki>{{LILYDEVELDOC}} → https://lilypond.org/docs/{{LILYDEVEL}}/Documentation</nowiki>

Such variables would reduce maintainance of yet-to-be-written templates. In particular, I would like to add <code><nowiki>Template:convert-ly</nowiki></code>: it would tell users that the snippet in question needs conversion with <code>convert-ly</code> (showing a link to the documentation) for newer versions. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:46, 28 December 2025 (UTC)

:Sounds OK to me. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:34, 28 December 2025 (UTC)
::Great! However, it seems to me that you have to add some piece of PHP code to do that... This means I cannot do it by myself. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 07:00, 30 December 2025 (UTC)
:::Ah, do you need them to be variables as opposed to templates? [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:30, 30 December 2025 (UTC)
::::Do I? I honestly don't know. Please advise. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 12:36, 30 December 2025 (UTC)
:::::Please try templates first. Seems to me that the use case for variables is when you want programmatically generated stuff like the current date. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 19:40, 30 December 2025 (UTC)
::::::It seems to work fine, thanks! However, for more serious template handling I think that the [https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions ParserFunctions] extension would be necessary. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 06:43, 31 December 2025 (UTC)
:::::::Added. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:01, 31 December 2025 (UTC)
::::::::Thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 14:41, 1 January 2026 (UTC)

User talk:Jean Abou Samra

2025-12-31T08:01:47Z

Jean Abou Samra: /* MediaWiki variables for current stable and unstable LilyPond versions */ Reply

== Test of email notifications ==

This is a test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 02:46, 2 November 2025 (UTC)

:Another test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:04, 2 November 2025 (UTC)
::Third test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:05, 2 November 2025 (UTC)
:::Reply test. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 03:05, 2 November 2025 (UTC)
::::Yet another test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:14, 2 November 2025 (UTC)

== Default stylesheet for the Wiki ==

Jean,

you've recently removed paper indentation settings from [[Rest styles]], arguing that no indentation is the default for this Wiki. However, this snippet is part of the “official” documentation that doesn't set the indentation to zero by default...

I thus wonder whether it makes sense to synchronize the Wiki with the LilyPond documentation by not providing a default value for the indentation. Another reason to stay with LilyPond's default is that a novice user who tries to compile a snippet might be surprised that it looks differently. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 16:51, 23 November 2025 (UTC)

:I'm surprised. [https://lilypond.org/doc/v2.25/Documentation/contributor/lilypond-formatting This page of the contributor's guide] implies <code>indent = 0</code> is the default in doc snippets. Is it out of date? What are the exact settings used to compile snippets in the docs? It's been too long since I had any idea how the doc build works, I can't find this in the repo right now… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:13, 23 November 2025 (UTC)
::I took the style settings used on the wiki [https://lilypond.org/doc/v2.25/Documentation/usage/other-programs right from the usage manual] in the section that says "you have to effectively mimick how lilypond-book runs lilypond"… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:15, 23 November 2025 (UTC)
:::D'oh. You are correct. My mistake, my memory failed me, and of course I didn't check before writing :-)
:::Sorry for the noise -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:22, 23 November 2025 (UTC)

== cropped SVG images ==

Jean, please have a look at the image in [[Custodes]] – the mensural custodes in the fourth staff are cropped. If you download the SVG image and use a program like `inkview` you can see that the image actually contains the complete glyphs, however, the bounding box is too tight (an old LilyPond issue, as you certainly know).

Is there a possibility to increase the bounding boxes of all images (both horizontally and vertically) using a post-processing step so that cropping can be avoided? -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 10:40, 25 November 2025 (UTC)

:Seems a bit overkill to me. I've added a simple workaround to that snippet. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 12:41, 25 November 2025 (UTC)
::Nice, thanks! I didn't think of this simple fix. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:27, 25 November 2025 (UTC)

== Some CSS code for <nowiki><samp></nowiki> ==

Jean, what do you think of adding something like the following

<pre>
body { quotes: '‘' '’'; }
samp:before { content: open-quote; }
samp:after { content: close-quote; }
</pre>

to the Wiki CSS for the sake of better conversion to Texinfo? My reasoning is as follows.

There is a strong visual difference between <code><nowiki><code></nowiki></code> in the Wiki and <code>@code</code> in Texinfo output: the former produces typewriter text in a box, the latter uses just typewriter. This is fine with the fonts used for Texinfo output except for marking single letters: in Texinfo it is better to use <code>@samp</code> for this situation, producing typewriter text in quotes.

On the Wiki side I would thus like to use <code><nowiki><samp></nowiki></code>, which <code>makelsr.pl</code> converts to <code>@samp</code>. However, it currently produces plain typewriter in the Wiki, which isn't ideal since the contrast to plain text isn't large enough IMHO.

Example: The letter <samp>s</samp> is marked with <code><nowiki><samp></nowiki></code>. My suggestion: The letter ‘<samp>s</samp>’ is marked with <code><nowiki><samp></nowiki></code>.

An alternative would be to give <code><nowiki><samp></nowiki></code> the same appearance as <code><nowiki><code></nowiki></code>. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:15, 30 November 2025 (UTC)

:Done. Thanks for providing the CSS code. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 15:28, 6 December 2025 (UTC)

:: Ah, I missed that with this CSS code the quote characters are also in typewriter, which is not correct. So please add <code>font-family: sans-serif;</code> to both the <code>samp:before</code> and <code>samp:after</code> block.
:: [I haven't found out how to display the quotes with the same font selected by the user to display the main font in Wiki – or is this fixed to always be sans-serif?]

::: Done. I don't know a better solution either. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 14:30, 8 December 2025 (UTC)
:::Thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:48, 9 December 2025 (UTC)

== Search issues ==

Jean,

To get nice snippet headings in the documentation, we often use non-letter stuff like opening and closing quotes in Wiki page titles. However, as I've found out recently, this severely hampers searching. For example, the snippet [[Using \arpeggioBracket to make divisi more visible]] cannot be immediately found by entering “Using arpeggioBracket” (i.e., without the backslash) into the search field.

I now wonder whether the Wiki can be configured to ignore quote characters and the like in the search. If this is not possible, I have to add redirections for all articles with such characters in its name. It's not a big deal since it can be done programmatically, however, not needing this would be a better solution. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:55, 9 December 2025 (UTC)

:AFAIU the autocompletion just matches by title prefix (to be clear, this is not about the search results page you get if you press Enter, which is much more complete). I think it's not too bad, not sure if there's any way to change it. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 14:13, 9 December 2025 (UTC)
::OK, thanks. What do you think of installing the [https://www.mediawiki.org/wiki/Extension:CirrusSearch Cirrus search extension]? It seems that Wikimedia is using this by default, and it comes with fuzzy search support, AFAICS. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 14:47, 9 December 2025 (UTC)
:::It looks like there is no opensearch package in Fedora, and honestly I'm not too keen on setting up a tool as large and complex as MediaWiki itself requiring its own systemd services and networks ports and so on if it's only for the sake of this autocompletion… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:20, 12 December 2025 (UTC)

== More fonts for the Wiki ==

Jean,

please have a look at the snippet [[Changing the default text font family]]: as can be seen, some font shapes for DejaVu Mono are missing. Is it possible to get them added to the server that runs the Wiki?

BTW, the same holds for the [[UTF-8]] snippet, where Japanese is missing.
-- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 15:39, 12 December 2025 (UTC)

:Fixed. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:34, 12 December 2025 (UTC)
::Thanks, but are you sure that the CJK font is working correctly? I tried to modify the [[UTF-8]] snippet to trigger a re-rendering, but I still can't see any Japanese... -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 20:44, 12 December 2025 (UTC)
:::Oops, indeed. But I don't understand why. On the server, <code>-dshow-available-fonts</code> does list "Noto Serif CJK JP". And curiously, if I remove all font settings and compile the code with different versions, it starts working between 2.25.12 and 2.25.13. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 23:49, 12 December 2025 (UTC)
::::Ah, I forgot that Google added Font Variation (VF) versions of the CJK fonts, and the various GNU/Linux distros eagerly took them to make the font bundles much smaller. Older LilyPond versions cannot reject these fonts correctly.
::::For me it works with 2.24.4 if you use the font <code>[https://github.com/notofonts/noto-cjk/blob/main/Serif/OTF/Japanese/NotoSerifCJKjp-Regular.otf NotoSerifCJKjp-Regular.otf]</code> (probably also installing the [https://github.com/notofonts/noto-cjk/blob/main/Serif/OTF/Japanese/NotoSerifCJKjp-Bold.otf bold version] for completeness), and this font is found first. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 04:24, 13 December 2025 (UTC)
:::::Thanks, I've added these fonts on the server as a workaround. The snippet now displays correctly. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 09:13, 13 December 2025 (UTC)
::::::Great, thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 10:50, 13 December 2025 (UTC)

== This wiki has no templates ==

Would it be ok if I created some templates? And I am missing several AddOns, CharInsert would be nice for editing, SyntaxHighlight, Scribunto. I am running a rather private Lilypond Wiki in German for several years and have some experience with Wikis, [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 15:13, 18 December 2025 (UTC)

:Feel free to create all kinds of pages, including templates. However, I'd prefer if they were created as needed for specific pages (i.e., don't create templates "for the future" that aren't used on any pages). Also, I don't see much that could be factored between pages so what's your use case? In particular, please don't create templates similar [[wikipedia:Template:Em|<code><nowiki>{{em|...}}</nowiki></code> on Wikipedia]] that add friction to the editing process for a negligible payoff.
:I haven't installed the extensions you requested because:
:# I don't see any special characters that would be needed particularly often on this wiki specifically, and I'd rather not maintain a general list of special characters, this is the job of system-level input methods like Compose keys and character map apps IMHO.
:# It wouldn't make much sense to have syntax highlighting only for the few code snippets that use <code><nowiki><pre></nowiki></code>, as opposed to <code><nowiki><lilypond></nowiki></code>. However, if someone submits a change for adding syntax highlighting to the output of <code><nowiki><lilypond></nowiki></code> in the [https://gitlab.com/jeanas/LilyWiki extension] that defines this tag for the wiki, I'll be happy to review it.
:# Scribunto has security implications (e.g., the need to keep Lua updated), so I'd rather only install it if there is a compelling use case for that.
:[[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 21:10, 18 December 2025 (UTC)
::Thank you for your answer. You have a point with security issues, SyntaxHighlight needs Scribunto. There is no special language support for Lilypond anyway, I use Latex, better than nothing. Your installation has to offer proc open, otherwise Scribunto is not working. I have not found a single provider which allows this.
::Maybe I am missing something in my preferences, when editing I do not see anything that supports editing, not even the option to insert links, maybe it's because I don't use the visual editor, I like "pure" editing as it is in Lilypond. CharInsert offers support for Wiki syntax, including tags like <pre>, all combinations of {} and so on.
::Greetings from Austria, [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 03:17, 19 December 2025 (UTC)
:::[off-topic] Where in Austria? Greetings from Kufstein :-) -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:15, 19 December 2025 (UTC)
::::Niederösterreich, nordöstlich von Wien (Bezirk Gänserndorf) [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 15:21, 19 December 2025 (UTC)
:::I don't think SyntaxHighlight needs Scribunto. It uses Pygments, which is a Python (not Lua) library (of which I actually am technically a maintainer, although I've been inactive lately by lack of time). It certainly needs something like <code>exec</code>/<code>proc_open</code>, but this wiki doesn't use a "managed" MediaWiki install (where the provider installs things for you, à la "Wordpress in one click"), it's on a VPS on which I have root access and administrate things myself, so I can install and configure anything (and <code>exec</code> is already being used to run LilyPond). The real problem is that the LilyPond code snippets are mostly added through a the special, non-standard parser tag <code><nowiki><lilypond></nowiki></code> and so the extension I wrote that defines this tag would need to support syntax highlighting.
:::Regarding the editor toolbar, it sounds like what you want is not CharInsert but [https://www.mediawiki.org/wiki/Extension:WikiEditor WikiEditor], which I've just added. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:15, 19 December 2025 (UTC)
::::PS: I also meant to write that Pygments supports LilyPond. (I implemented this a few years ago.) [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:26, 19 December 2025 (UTC)
:::::Apropos Pygments: I've submitted a [https://github.com/pygments/pygments/pull/2974 PR] to update LilyPond support some time ago. [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:38, 19 December 2025 (UTC)
::::Thank you for installing this extension, this is definitely an improvement. CharInsert is a different animal. Root access is of course best, but you have to do much administration. Usually root access is very expensive when you need a provider. A long time ago I have written a Lilypond extension myself on a home server in my local network.
::::Just in case you are asking who I am, I wrote LSR 1040, 1042, 1043, 1044 (when I remember right) and was involved in 1066 and 1067. [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 19:34, 19 December 2025 (UTC)

== MediaWiki variables for current stable and unstable LilyPond versions ==

Jean,

what do you think about adding [https://www.mediawiki.org/wiki/Manual:Variable MediaWiki variables] that indicate the current stable and unstable LilyPond versions (without the ‘micro’ value)? I suggest

<nowiki>{{LILYSTABLE}}</nowiki> → 2.24
<nowiki>{{LILYDEVEL}}</nowiki> → 2.25

and maybe

<nowiki>{{LILYSTABLEDOC}} → https://lilypond.org/docs/{{LILYSTABLE}}/Documentation</nowiki>
<nowiki>{{LILYDEVELDOC}} → https://lilypond.org/docs/{{LILYDEVEL}}/Documentation</nowiki>

Such variables would reduce maintainance of yet-to-be-written templates. In particular, I would like to add <code><nowiki>Template:convert-ly</nowiki></code>: it would tell users that the snippet in question needs conversion with <code>convert-ly</code> (showing a link to the documentation) for newer versions. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:46, 28 December 2025 (UTC)

:Sounds OK to me. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:34, 28 December 2025 (UTC)
::Great! However, it seems to me that you have to add some piece of PHP code to do that... This means I cannot do it by myself. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 07:00, 30 December 2025 (UTC)
:::Ah, do you need them to be variables as opposed to templates? [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:30, 30 December 2025 (UTC)
::::Do I? I honestly don't know. Please advise. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 12:36, 30 December 2025 (UTC)
:::::Please try templates first. Seems to me that the use case for variables is when you want programmatically generated stuff like the current date. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 19:40, 30 December 2025 (UTC)
::::::It seems to work fine, thanks! However, for more serious template handling I think that the [https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions ParserFunctions] extension would be necessary. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 06:43, 31 December 2025 (UTC)
:::::::Added. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:01, 31 December 2025 (UTC)

User talk:Jean Abou Samra

2025-12-30T19:40:49Z

Jean Abou Samra: /* MediaWiki variables for current stable and unstable LilyPond versions */ Reply

== Test of email notifications ==

This is a test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 02:46, 2 November 2025 (UTC)

:Another test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:04, 2 November 2025 (UTC)
::Third test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:05, 2 November 2025 (UTC)
:::Reply test. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 03:05, 2 November 2025 (UTC)
::::Yet another test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:14, 2 November 2025 (UTC)

== Default stylesheet for the Wiki ==

Jean,

you've recently removed paper indentation settings from [[Rest styles]], arguing that no indentation is the default for this Wiki. However, this snippet is part of the “official” documentation that doesn't set the indentation to zero by default...

I thus wonder whether it makes sense to synchronize the Wiki with the LilyPond documentation by not providing a default value for the indentation. Another reason to stay with LilyPond's default is that a novice user who tries to compile a snippet might be surprised that it looks differently. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 16:51, 23 November 2025 (UTC)

:I'm surprised. [https://lilypond.org/doc/v2.25/Documentation/contributor/lilypond-formatting This page of the contributor's guide] implies <code>indent = 0</code> is the default in doc snippets. Is it out of date? What are the exact settings used to compile snippets in the docs? It's been too long since I had any idea how the doc build works, I can't find this in the repo right now… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:13, 23 November 2025 (UTC)
::I took the style settings used on the wiki [https://lilypond.org/doc/v2.25/Documentation/usage/other-programs right from the usage manual] in the section that says "you have to effectively mimick how lilypond-book runs lilypond"… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:15, 23 November 2025 (UTC)
:::D'oh. You are correct. My mistake, my memory failed me, and of course I didn't check before writing :-)
:::Sorry for the noise -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:22, 23 November 2025 (UTC)

== cropped SVG images ==

Jean, please have a look at the image in [[Custodes]] – the mensural custodes in the fourth staff are cropped. If you download the SVG image and use a program like `inkview` you can see that the image actually contains the complete glyphs, however, the bounding box is too tight (an old LilyPond issue, as you certainly know).

Is there a possibility to increase the bounding boxes of all images (both horizontally and vertically) using a post-processing step so that cropping can be avoided? -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 10:40, 25 November 2025 (UTC)

:Seems a bit overkill to me. I've added a simple workaround to that snippet. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 12:41, 25 November 2025 (UTC)
::Nice, thanks! I didn't think of this simple fix. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:27, 25 November 2025 (UTC)

== Some CSS code for <nowiki><samp></nowiki> ==

Jean, what do you think of adding something like the following

<pre>
body { quotes: '‘' '’'; }
samp:before { content: open-quote; }
samp:after { content: close-quote; }
</pre>

to the Wiki CSS for the sake of better conversion to Texinfo? My reasoning is as follows.

There is a strong visual difference between <code><nowiki><code></nowiki></code> in the Wiki and <code>@code</code> in Texinfo output: the former produces typewriter text in a box, the latter uses just typewriter. This is fine with the fonts used for Texinfo output except for marking single letters: in Texinfo it is better to use <code>@samp</code> for this situation, producing typewriter text in quotes.

On the Wiki side I would thus like to use <code><nowiki><samp></nowiki></code>, which <code>makelsr.pl</code> converts to <code>@samp</code>. However, it currently produces plain typewriter in the Wiki, which isn't ideal since the contrast to plain text isn't large enough IMHO.

Example: The letter <samp>s</samp> is marked with <code><nowiki><samp></nowiki></code>. My suggestion: The letter ‘<samp>s</samp>’ is marked with <code><nowiki><samp></nowiki></code>.

An alternative would be to give <code><nowiki><samp></nowiki></code> the same appearance as <code><nowiki><code></nowiki></code>. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:15, 30 November 2025 (UTC)

:Done. Thanks for providing the CSS code. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 15:28, 6 December 2025 (UTC)

:: Ah, I missed that with this CSS code the quote characters are also in typewriter, which is not correct. So please add <code>font-family: sans-serif;</code> to both the <code>samp:before</code> and <code>samp:after</code> block.
:: [I haven't found out how to display the quotes with the same font selected by the user to display the main font in Wiki – or is this fixed to always be sans-serif?]

::: Done. I don't know a better solution either. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 14:30, 8 December 2025 (UTC)
:::Thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:48, 9 December 2025 (UTC)

== Search issues ==

Jean,

To get nice snippet headings in the documentation, we often use non-letter stuff like opening and closing quotes in Wiki page titles. However, as I've found out recently, this severely hampers searching. For example, the snippet [[Using \arpeggioBracket to make divisi more visible]] cannot be immediately found by entering “Using arpeggioBracket” (i.e., without the backslash) into the search field.

I now wonder whether the Wiki can be configured to ignore quote characters and the like in the search. If this is not possible, I have to add redirections for all articles with such characters in its name. It's not a big deal since it can be done programmatically, however, not needing this would be a better solution. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:55, 9 December 2025 (UTC)

:AFAIU the autocompletion just matches by title prefix (to be clear, this is not about the search results page you get if you press Enter, which is much more complete). I think it's not too bad, not sure if there's any way to change it. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 14:13, 9 December 2025 (UTC)
::OK, thanks. What do you think of installing the [https://www.mediawiki.org/wiki/Extension:CirrusSearch Cirrus search extension]? It seems that Wikimedia is using this by default, and it comes with fuzzy search support, AFAICS. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 14:47, 9 December 2025 (UTC)
:::It looks like there is no opensearch package in Fedora, and honestly I'm not too keen on setting up a tool as large and complex as MediaWiki itself requiring its own systemd services and networks ports and so on if it's only for the sake of this autocompletion… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:20, 12 December 2025 (UTC)

== More fonts for the Wiki ==

Jean,

please have a look at the snippet [[Changing the default text font family]]: as can be seen, some font shapes for DejaVu Mono are missing. Is it possible to get them added to the server that runs the Wiki?

BTW, the same holds for the [[UTF-8]] snippet, where Japanese is missing.
-- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 15:39, 12 December 2025 (UTC)

:Fixed. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:34, 12 December 2025 (UTC)
::Thanks, but are you sure that the CJK font is working correctly? I tried to modify the [[UTF-8]] snippet to trigger a re-rendering, but I still can't see any Japanese... -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 20:44, 12 December 2025 (UTC)
:::Oops, indeed. But I don't understand why. On the server, <code>-dshow-available-fonts</code> does list "Noto Serif CJK JP". And curiously, if I remove all font settings and compile the code with different versions, it starts working between 2.25.12 and 2.25.13. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 23:49, 12 December 2025 (UTC)
::::Ah, I forgot that Google added Font Variation (VF) versions of the CJK fonts, and the various GNU/Linux distros eagerly took them to make the font bundles much smaller. Older LilyPond versions cannot reject these fonts correctly.
::::For me it works with 2.24.4 if you use the font <code>[https://github.com/notofonts/noto-cjk/blob/main/Serif/OTF/Japanese/NotoSerifCJKjp-Regular.otf NotoSerifCJKjp-Regular.otf]</code> (probably also installing the [https://github.com/notofonts/noto-cjk/blob/main/Serif/OTF/Japanese/NotoSerifCJKjp-Bold.otf bold version] for completeness), and this font is found first. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 04:24, 13 December 2025 (UTC)
:::::Thanks, I've added these fonts on the server as a workaround. The snippet now displays correctly. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 09:13, 13 December 2025 (UTC)
::::::Great, thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 10:50, 13 December 2025 (UTC)

== This wiki has no templates ==

Would it be ok if I created some templates? And I am missing several AddOns, CharInsert would be nice for editing, SyntaxHighlight, Scribunto. I am running a rather private Lilypond Wiki in German for several years and have some experience with Wikis, [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 15:13, 18 December 2025 (UTC)

:Feel free to create all kinds of pages, including templates. However, I'd prefer if they were created as needed for specific pages (i.e., don't create templates "for the future" that aren't used on any pages). Also, I don't see much that could be factored between pages so what's your use case? In particular, please don't create templates similar [[wikipedia:Template:Em|<code><nowiki>{{em|...}}</nowiki></code> on Wikipedia]] that add friction to the editing process for a negligible payoff.
:I haven't installed the extensions you requested because:
:# I don't see any special characters that would be needed particularly often on this wiki specifically, and I'd rather not maintain a general list of special characters, this is the job of system-level input methods like Compose keys and character map apps IMHO.
:# It wouldn't make much sense to have syntax highlighting only for the few code snippets that use <code><nowiki><pre></nowiki></code>, as opposed to <code><nowiki><lilypond></nowiki></code>. However, if someone submits a change for adding syntax highlighting to the output of <code><nowiki><lilypond></nowiki></code> in the [https://gitlab.com/jeanas/LilyWiki extension] that defines this tag for the wiki, I'll be happy to review it.
:# Scribunto has security implications (e.g., the need to keep Lua updated), so I'd rather only install it if there is a compelling use case for that.
:[[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 21:10, 18 December 2025 (UTC)
::Thank you for your answer. You have a point with security issues, SyntaxHighlight needs Scribunto. There is no special language support for Lilypond anyway, I use Latex, better than nothing. Your installation has to offer proc open, otherwise Scribunto is not working. I have not found a single provider which allows this.
::Maybe I am missing something in my preferences, when editing I do not see anything that supports editing, not even the option to insert links, maybe it's because I don't use the visual editor, I like "pure" editing as it is in Lilypond. CharInsert offers support for Wiki syntax, including tags like <pre>, all combinations of {} and so on.
::Greetings from Austria, [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 03:17, 19 December 2025 (UTC)
:::[off-topic] Where in Austria? Greetings from Kufstein :-) -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:15, 19 December 2025 (UTC)
::::Niederösterreich, nordöstlich von Wien (Bezirk Gänserndorf) [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 15:21, 19 December 2025 (UTC)
:::I don't think SyntaxHighlight needs Scribunto. It uses Pygments, which is a Python (not Lua) library (of which I actually am technically a maintainer, although I've been inactive lately by lack of time). It certainly needs something like <code>exec</code>/<code>proc_open</code>, but this wiki doesn't use a "managed" MediaWiki install (where the provider installs things for you, à la "Wordpress in one click"), it's on a VPS on which I have root access and administrate things myself, so I can install and configure anything (and <code>exec</code> is already being used to run LilyPond). The real problem is that the LilyPond code snippets are mostly added through a the special, non-standard parser tag <code><nowiki><lilypond></nowiki></code> and so the extension I wrote that defines this tag would need to support syntax highlighting.
:::Regarding the editor toolbar, it sounds like what you want is not CharInsert but [https://www.mediawiki.org/wiki/Extension:WikiEditor WikiEditor], which I've just added. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:15, 19 December 2025 (UTC)
::::PS: I also meant to write that Pygments supports LilyPond. (I implemented this a few years ago.) [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:26, 19 December 2025 (UTC)
:::::Apropos Pygments: I've submitted a [https://github.com/pygments/pygments/pull/2974 PR] to update LilyPond support some time ago. [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:38, 19 December 2025 (UTC)
::::Thank you for installing this extension, this is definitely an improvement. CharInsert is a different animal. Root access is of course best, but you have to do much administration. Usually root access is very expensive when you need a provider. A long time ago I have written a Lilypond extension myself on a home server in my local network.
::::Just in case you are asking who I am, I wrote LSR 1040, 1042, 1043, 1044 (when I remember right) and was involved in 1066 and 1067. [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 19:34, 19 December 2025 (UTC)

== MediaWiki variables for current stable and unstable LilyPond versions ==

Jean,

what do you think about adding [https://www.mediawiki.org/wiki/Manual:Variable MediaWiki variables] that indicate the current stable and unstable LilyPond versions (without the ‘micro’ value)? I suggest

<nowiki>{{LILYSTABLE}}</nowiki> → 2.24
<nowiki>{{LILYDEVEL}}</nowiki> → 2.25

and maybe

<nowiki>{{LILYSTABLEDOC}} → https://lilypond.org/docs/{{LILYSTABLE}}/Documentation</nowiki>
<nowiki>{{LILYDEVELDOC}} → https://lilypond.org/docs/{{LILYDEVEL}}/Documentation</nowiki>

Such variables would reduce maintainance of yet-to-be-written templates. In particular, I would like to add <code><nowiki>Template:convert-ly</nowiki></code>: it would tell users that the snippet in question needs conversion with <code>convert-ly</code> (showing a link to the documentation) for newer versions. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:46, 28 December 2025 (UTC)

:Sounds OK to me. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:34, 28 December 2025 (UTC)
::Great! However, it seems to me that you have to add some piece of PHP code to do that... This means I cannot do it by myself. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 07:00, 30 December 2025 (UTC)
:::Ah, do you need them to be variables as opposed to templates? [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:30, 30 December 2025 (UTC)
::::Do I? I honestly don't know. Please advise. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 12:36, 30 December 2025 (UTC)
:::::Please try templates first. Seems to me that the use case for variables is when you want programmatically generated stuff like the current date. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 19:40, 30 December 2025 (UTC)

User talk:Jean Abou Samra

2025-12-30T08:30:20Z

Jean Abou Samra: /* MediaWiki variables for current stable and unstable LilyPond versions */ Reply

== Test of email notifications ==

This is a test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 02:46, 2 November 2025 (UTC)

:Another test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:04, 2 November 2025 (UTC)
::Third test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:05, 2 November 2025 (UTC)
:::Reply test. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 03:05, 2 November 2025 (UTC)
::::Yet another test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:14, 2 November 2025 (UTC)

== Default stylesheet for the Wiki ==

Jean,

you've recently removed paper indentation settings from [[Rest styles]], arguing that no indentation is the default for this Wiki. However, this snippet is part of the “official” documentation that doesn't set the indentation to zero by default...

I thus wonder whether it makes sense to synchronize the Wiki with the LilyPond documentation by not providing a default value for the indentation. Another reason to stay with LilyPond's default is that a novice user who tries to compile a snippet might be surprised that it looks differently. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 16:51, 23 November 2025 (UTC)

:I'm surprised. [https://lilypond.org/doc/v2.25/Documentation/contributor/lilypond-formatting This page of the contributor's guide] implies <code>indent = 0</code> is the default in doc snippets. Is it out of date? What are the exact settings used to compile snippets in the docs? It's been too long since I had any idea how the doc build works, I can't find this in the repo right now… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:13, 23 November 2025 (UTC)
::I took the style settings used on the wiki [https://lilypond.org/doc/v2.25/Documentation/usage/other-programs right from the usage manual] in the section that says "you have to effectively mimick how lilypond-book runs lilypond"… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:15, 23 November 2025 (UTC)
:::D'oh. You are correct. My mistake, my memory failed me, and of course I didn't check before writing :-)
:::Sorry for the noise -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:22, 23 November 2025 (UTC)

== cropped SVG images ==

Jean, please have a look at the image in [[Custodes]] – the mensural custodes in the fourth staff are cropped. If you download the SVG image and use a program like `inkview` you can see that the image actually contains the complete glyphs, however, the bounding box is too tight (an old LilyPond issue, as you certainly know).

Is there a possibility to increase the bounding boxes of all images (both horizontally and vertically) using a post-processing step so that cropping can be avoided? -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 10:40, 25 November 2025 (UTC)

:Seems a bit overkill to me. I've added a simple workaround to that snippet. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 12:41, 25 November 2025 (UTC)
::Nice, thanks! I didn't think of this simple fix. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:27, 25 November 2025 (UTC)

== Some CSS code for <nowiki><samp></nowiki> ==

Jean, what do you think of adding something like the following

<pre>
body { quotes: '‘' '’'; }
samp:before { content: open-quote; }
samp:after { content: close-quote; }
</pre>

to the Wiki CSS for the sake of better conversion to Texinfo? My reasoning is as follows.

There is a strong visual difference between <code><nowiki><code></nowiki></code> in the Wiki and <code>@code</code> in Texinfo output: the former produces typewriter text in a box, the latter uses just typewriter. This is fine with the fonts used for Texinfo output except for marking single letters: in Texinfo it is better to use <code>@samp</code> for this situation, producing typewriter text in quotes.

On the Wiki side I would thus like to use <code><nowiki><samp></nowiki></code>, which <code>makelsr.pl</code> converts to <code>@samp</code>. However, it currently produces plain typewriter in the Wiki, which isn't ideal since the contrast to plain text isn't large enough IMHO.

Example: The letter <samp>s</samp> is marked with <code><nowiki><samp></nowiki></code>. My suggestion: The letter ‘<samp>s</samp>’ is marked with <code><nowiki><samp></nowiki></code>.

An alternative would be to give <code><nowiki><samp></nowiki></code> the same appearance as <code><nowiki><code></nowiki></code>. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:15, 30 November 2025 (UTC)

:Done. Thanks for providing the CSS code. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 15:28, 6 December 2025 (UTC)

:: Ah, I missed that with this CSS code the quote characters are also in typewriter, which is not correct. So please add <code>font-family: sans-serif;</code> to both the <code>samp:before</code> and <code>samp:after</code> block.
:: [I haven't found out how to display the quotes with the same font selected by the user to display the main font in Wiki – or is this fixed to always be sans-serif?]

::: Done. I don't know a better solution either. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 14:30, 8 December 2025 (UTC)
:::Thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:48, 9 December 2025 (UTC)

== Search issues ==

Jean,

To get nice snippet headings in the documentation, we often use non-letter stuff like opening and closing quotes in Wiki page titles. However, as I've found out recently, this severely hampers searching. For example, the snippet [[Using \arpeggioBracket to make divisi more visible]] cannot be immediately found by entering “Using arpeggioBracket” (i.e., without the backslash) into the search field.

I now wonder whether the Wiki can be configured to ignore quote characters and the like in the search. If this is not possible, I have to add redirections for all articles with such characters in its name. It's not a big deal since it can be done programmatically, however, not needing this would be a better solution. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:55, 9 December 2025 (UTC)

:AFAIU the autocompletion just matches by title prefix (to be clear, this is not about the search results page you get if you press Enter, which is much more complete). I think it's not too bad, not sure if there's any way to change it. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 14:13, 9 December 2025 (UTC)
::OK, thanks. What do you think of installing the [https://www.mediawiki.org/wiki/Extension:CirrusSearch Cirrus search extension]? It seems that Wikimedia is using this by default, and it comes with fuzzy search support, AFAICS. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 14:47, 9 December 2025 (UTC)
:::It looks like there is no opensearch package in Fedora, and honestly I'm not too keen on setting up a tool as large and complex as MediaWiki itself requiring its own systemd services and networks ports and so on if it's only for the sake of this autocompletion… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:20, 12 December 2025 (UTC)

== More fonts for the Wiki ==

Jean,

please have a look at the snippet [[Changing the default text font family]]: as can be seen, some font shapes for DejaVu Mono are missing. Is it possible to get them added to the server that runs the Wiki?

BTW, the same holds for the [[UTF-8]] snippet, where Japanese is missing.
-- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 15:39, 12 December 2025 (UTC)

:Fixed. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:34, 12 December 2025 (UTC)
::Thanks, but are you sure that the CJK font is working correctly? I tried to modify the [[UTF-8]] snippet to trigger a re-rendering, but I still can't see any Japanese... -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 20:44, 12 December 2025 (UTC)
:::Oops, indeed. But I don't understand why. On the server, <code>-dshow-available-fonts</code> does list "Noto Serif CJK JP". And curiously, if I remove all font settings and compile the code with different versions, it starts working between 2.25.12 and 2.25.13. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 23:49, 12 December 2025 (UTC)
::::Ah, I forgot that Google added Font Variation (VF) versions of the CJK fonts, and the various GNU/Linux distros eagerly took them to make the font bundles much smaller. Older LilyPond versions cannot reject these fonts correctly.
::::For me it works with 2.24.4 if you use the font <code>[https://github.com/notofonts/noto-cjk/blob/main/Serif/OTF/Japanese/NotoSerifCJKjp-Regular.otf NotoSerifCJKjp-Regular.otf]</code> (probably also installing the [https://github.com/notofonts/noto-cjk/blob/main/Serif/OTF/Japanese/NotoSerifCJKjp-Bold.otf bold version] for completeness), and this font is found first. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 04:24, 13 December 2025 (UTC)
:::::Thanks, I've added these fonts on the server as a workaround. The snippet now displays correctly. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 09:13, 13 December 2025 (UTC)
::::::Great, thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 10:50, 13 December 2025 (UTC)

== This wiki has no templates ==

Would it be ok if I created some templates? And I am missing several AddOns, CharInsert would be nice for editing, SyntaxHighlight, Scribunto. I am running a rather private Lilypond Wiki in German for several years and have some experience with Wikis, [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 15:13, 18 December 2025 (UTC)

:Feel free to create all kinds of pages, including templates. However, I'd prefer if they were created as needed for specific pages (i.e., don't create templates "for the future" that aren't used on any pages). Also, I don't see much that could be factored between pages so what's your use case? In particular, please don't create templates similar [[wikipedia:Template:Em|<code><nowiki>{{em|...}}</nowiki></code> on Wikipedia]] that add friction to the editing process for a negligible payoff.
:I haven't installed the extensions you requested because:
:# I don't see any special characters that would be needed particularly often on this wiki specifically, and I'd rather not maintain a general list of special characters, this is the job of system-level input methods like Compose keys and character map apps IMHO.
:# It wouldn't make much sense to have syntax highlighting only for the few code snippets that use <code><nowiki><pre></nowiki></code>, as opposed to <code><nowiki><lilypond></nowiki></code>. However, if someone submits a change for adding syntax highlighting to the output of <code><nowiki><lilypond></nowiki></code> in the [https://gitlab.com/jeanas/LilyWiki extension] that defines this tag for the wiki, I'll be happy to review it.
:# Scribunto has security implications (e.g., the need to keep Lua updated), so I'd rather only install it if there is a compelling use case for that.
:[[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 21:10, 18 December 2025 (UTC)
::Thank you for your answer. You have a point with security issues, SyntaxHighlight needs Scribunto. There is no special language support for Lilypond anyway, I use Latex, better than nothing. Your installation has to offer proc open, otherwise Scribunto is not working. I have not found a single provider which allows this.
::Maybe I am missing something in my preferences, when editing I do not see anything that supports editing, not even the option to insert links, maybe it's because I don't use the visual editor, I like "pure" editing as it is in Lilypond. CharInsert offers support for Wiki syntax, including tags like <pre>, all combinations of {} and so on.
::Greetings from Austria, [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 03:17, 19 December 2025 (UTC)
:::[off-topic] Where in Austria? Greetings from Kufstein :-) -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:15, 19 December 2025 (UTC)
::::Niederösterreich, nordöstlich von Wien (Bezirk Gänserndorf) [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 15:21, 19 December 2025 (UTC)
:::I don't think SyntaxHighlight needs Scribunto. It uses Pygments, which is a Python (not Lua) library (of which I actually am technically a maintainer, although I've been inactive lately by lack of time). It certainly needs something like <code>exec</code>/<code>proc_open</code>, but this wiki doesn't use a "managed" MediaWiki install (where the provider installs things for you, à la "Wordpress in one click"), it's on a VPS on which I have root access and administrate things myself, so I can install and configure anything (and <code>exec</code> is already being used to run LilyPond). The real problem is that the LilyPond code snippets are mostly added through a the special, non-standard parser tag <code><nowiki><lilypond></nowiki></code> and so the extension I wrote that defines this tag would need to support syntax highlighting.
:::Regarding the editor toolbar, it sounds like what you want is not CharInsert but [https://www.mediawiki.org/wiki/Extension:WikiEditor WikiEditor], which I've just added. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:15, 19 December 2025 (UTC)
::::PS: I also meant to write that Pygments supports LilyPond. (I implemented this a few years ago.) [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:26, 19 December 2025 (UTC)
:::::Apropos Pygments: I've submitted a [https://github.com/pygments/pygments/pull/2974 PR] to update LilyPond support some time ago. [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:38, 19 December 2025 (UTC)
::::Thank you for installing this extension, this is definitely an improvement. CharInsert is a different animal. Root access is of course best, but you have to do much administration. Usually root access is very expensive when you need a provider. A long time ago I have written a Lilypond extension myself on a home server in my local network.
::::Just in case you are asking who I am, I wrote LSR 1040, 1042, 1043, 1044 (when I remember right) and was involved in 1066 and 1067. [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 19:34, 19 December 2025 (UTC)

== MediaWiki variables for current stable and unstable LilyPond versions ==

Jean,

what do you think about adding [https://www.mediawiki.org/wiki/Manual:Variable MediaWiki variables] that indicate the current stable and unstable LilyPond versions (without the ‘micro’ value)? I suggest

<nowiki>{{LILYSTABLE}}</nowiki> → 2.24
<nowiki>{{LILYDEVEL}}</nowiki> → 2.25

and maybe

<nowiki>{{LILYSTABLEDOC}} → https://lilypond.org/docs/{{LILYSTABLE}}/Documentation</nowiki>
<nowiki>{{LILYDEVELDOC}} → https://lilypond.org/docs/{{LILYDEVEL}}/Documentation</nowiki>

Such variables would reduce maintainance of yet-to-be-written templates. In particular, I would like to add <code><nowiki>Template:convert-ly</nowiki></code>: it would tell users that the snippet in question needs conversion with <code>convert-ly</code> (showing a link to the documentation) for newer versions. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:46, 28 December 2025 (UTC)

:Sounds OK to me. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:34, 28 December 2025 (UTC)
::Great! However, it seems to me that you have to add some piece of PHP code to do that... This means I cannot do it by myself. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 07:00, 30 December 2025 (UTC)
:::Ah, do you need them to be variables as opposed to templates? [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:30, 30 December 2025 (UTC)

User talk:Jean Abou Samra

2025-12-28T08:34:49Z

Jean Abou Samra: /* MediaWiki variables for current stable and unstable LilyPond versions */ Reply

== Test of email notifications ==

This is a test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 02:46, 2 November 2025 (UTC)

:Another test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:04, 2 November 2025 (UTC)
::Third test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:05, 2 November 2025 (UTC)
:::Reply test. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 03:05, 2 November 2025 (UTC)
::::Yet another test. [[User:Jean Abou Samra Test Account|Jean Abou Samra Test Account]] ([[User talk:Jean Abou Samra Test Account|talk]]) 03:14, 2 November 2025 (UTC)

== Default stylesheet for the Wiki ==

Jean,

you've recently removed paper indentation settings from [[Rest styles]], arguing that no indentation is the default for this Wiki. However, this snippet is part of the “official” documentation that doesn't set the indentation to zero by default...

I thus wonder whether it makes sense to synchronize the Wiki with the LilyPond documentation by not providing a default value for the indentation. Another reason to stay with LilyPond's default is that a novice user who tries to compile a snippet might be surprised that it looks differently. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 16:51, 23 November 2025 (UTC)

:I'm surprised. [https://lilypond.org/doc/v2.25/Documentation/contributor/lilypond-formatting This page of the contributor's guide] implies <code>indent = 0</code> is the default in doc snippets. Is it out of date? What are the exact settings used to compile snippets in the docs? It's been too long since I had any idea how the doc build works, I can't find this in the repo right now… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:13, 23 November 2025 (UTC)
::I took the style settings used on the wiki [https://lilypond.org/doc/v2.25/Documentation/usage/other-programs right from the usage manual] in the section that says "you have to effectively mimick how lilypond-book runs lilypond"… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:15, 23 November 2025 (UTC)
:::D'oh. You are correct. My mistake, my memory failed me, and of course I didn't check before writing :-)
:::Sorry for the noise -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:22, 23 November 2025 (UTC)

== cropped SVG images ==

Jean, please have a look at the image in [[Custodes]] – the mensural custodes in the fourth staff are cropped. If you download the SVG image and use a program like `inkview` you can see that the image actually contains the complete glyphs, however, the bounding box is too tight (an old LilyPond issue, as you certainly know).

Is there a possibility to increase the bounding boxes of all images (both horizontally and vertically) using a post-processing step so that cropping can be avoided? -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 10:40, 25 November 2025 (UTC)

:Seems a bit overkill to me. I've added a simple workaround to that snippet. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 12:41, 25 November 2025 (UTC)
::Nice, thanks! I didn't think of this simple fix. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:27, 25 November 2025 (UTC)

== Some CSS code for <nowiki><samp></nowiki> ==

Jean, what do you think of adding something like the following

<pre>
body { quotes: '‘' '’'; }
samp:before { content: open-quote; }
samp:after { content: close-quote; }
</pre>

to the Wiki CSS for the sake of better conversion to Texinfo? My reasoning is as follows.

There is a strong visual difference between <code><nowiki><code></nowiki></code> in the Wiki and <code>@code</code> in Texinfo output: the former produces typewriter text in a box, the latter uses just typewriter. This is fine with the fonts used for Texinfo output except for marking single letters: in Texinfo it is better to use <code>@samp</code> for this situation, producing typewriter text in quotes.

On the Wiki side I would thus like to use <code><nowiki><samp></nowiki></code>, which <code>makelsr.pl</code> converts to <code>@samp</code>. However, it currently produces plain typewriter in the Wiki, which isn't ideal since the contrast to plain text isn't large enough IMHO.

Example: The letter <samp>s</samp> is marked with <code><nowiki><samp></nowiki></code>. My suggestion: The letter ‘<samp>s</samp>’ is marked with <code><nowiki><samp></nowiki></code>.

An alternative would be to give <code><nowiki><samp></nowiki></code> the same appearance as <code><nowiki><code></nowiki></code>. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:15, 30 November 2025 (UTC)

:Done. Thanks for providing the CSS code. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 15:28, 6 December 2025 (UTC)

:: Ah, I missed that with this CSS code the quote characters are also in typewriter, which is not correct. So please add <code>font-family: sans-serif;</code> to both the <code>samp:before</code> and <code>samp:after</code> block.
:: [I haven't found out how to display the quotes with the same font selected by the user to display the main font in Wiki – or is this fixed to always be sans-serif?]

::: Done. I don't know a better solution either. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 14:30, 8 December 2025 (UTC)
:::Thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:48, 9 December 2025 (UTC)

== Search issues ==

Jean,

To get nice snippet headings in the documentation, we often use non-letter stuff like opening and closing quotes in Wiki page titles. However, as I've found out recently, this severely hampers searching. For example, the snippet [[Using \arpeggioBracket to make divisi more visible]] cannot be immediately found by entering “Using arpeggioBracket” (i.e., without the backslash) into the search field.

I now wonder whether the Wiki can be configured to ignore quote characters and the like in the search. If this is not possible, I have to add redirections for all articles with such characters in its name. It's not a big deal since it can be done programmatically, however, not needing this would be a better solution. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 13:55, 9 December 2025 (UTC)

:AFAIU the autocompletion just matches by title prefix (to be clear, this is not about the search results page you get if you press Enter, which is much more complete). I think it's not too bad, not sure if there's any way to change it. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 14:13, 9 December 2025 (UTC)
::OK, thanks. What do you think of installing the [https://www.mediawiki.org/wiki/Extension:CirrusSearch Cirrus search extension]? It seems that Wikimedia is using this by default, and it comes with fuzzy search support, AFAICS. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 14:47, 9 December 2025 (UTC)
:::It looks like there is no opensearch package in Fedora, and honestly I'm not too keen on setting up a tool as large and complex as MediaWiki itself requiring its own systemd services and networks ports and so on if it's only for the sake of this autocompletion… [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:20, 12 December 2025 (UTC)

== More fonts for the Wiki ==

Jean,

please have a look at the snippet [[Changing the default text font family]]: as can be seen, some font shapes for DejaVu Mono are missing. Is it possible to get them added to the server that runs the Wiki?

BTW, the same holds for the [[UTF-8]] snippet, where Japanese is missing.
-- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 15:39, 12 December 2025 (UTC)

:Fixed. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 18:34, 12 December 2025 (UTC)
::Thanks, but are you sure that the CJK font is working correctly? I tried to modify the [[UTF-8]] snippet to trigger a re-rendering, but I still can't see any Japanese... -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 20:44, 12 December 2025 (UTC)
:::Oops, indeed. But I don't understand why. On the server, <code>-dshow-available-fonts</code> does list "Noto Serif CJK JP". And curiously, if I remove all font settings and compile the code with different versions, it starts working between 2.25.12 and 2.25.13. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 23:49, 12 December 2025 (UTC)
::::Ah, I forgot that Google added Font Variation (VF) versions of the CJK fonts, and the various GNU/Linux distros eagerly took them to make the font bundles much smaller. Older LilyPond versions cannot reject these fonts correctly.
::::For me it works with 2.24.4 if you use the font <code>[https://github.com/notofonts/noto-cjk/blob/main/Serif/OTF/Japanese/NotoSerifCJKjp-Regular.otf NotoSerifCJKjp-Regular.otf]</code> (probably also installing the [https://github.com/notofonts/noto-cjk/blob/main/Serif/OTF/Japanese/NotoSerifCJKjp-Bold.otf bold version] for completeness), and this font is found first. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 04:24, 13 December 2025 (UTC)
:::::Thanks, I've added these fonts on the server as a workaround. The snippet now displays correctly. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 09:13, 13 December 2025 (UTC)
::::::Great, thanks! -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 10:50, 13 December 2025 (UTC)

== This wiki has no templates ==

Would it be ok if I created some templates? And I am missing several AddOns, CharInsert would be nice for editing, SyntaxHighlight, Scribunto. I am running a rather private Lilypond Wiki in German for several years and have some experience with Wikis, [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 15:13, 18 December 2025 (UTC)

:Feel free to create all kinds of pages, including templates. However, I'd prefer if they were created as needed for specific pages (i.e., don't create templates "for the future" that aren't used on any pages). Also, I don't see much that could be factored between pages so what's your use case? In particular, please don't create templates similar [[wikipedia:Template:Em|<code><nowiki>{{em|...}}</nowiki></code> on Wikipedia]] that add friction to the editing process for a negligible payoff.
:I haven't installed the extensions you requested because:
:# I don't see any special characters that would be needed particularly often on this wiki specifically, and I'd rather not maintain a general list of special characters, this is the job of system-level input methods like Compose keys and character map apps IMHO.
:# It wouldn't make much sense to have syntax highlighting only for the few code snippets that use <code><nowiki><pre></nowiki></code>, as opposed to <code><nowiki><lilypond></nowiki></code>. However, if someone submits a change for adding syntax highlighting to the output of <code><nowiki><lilypond></nowiki></code> in the [https://gitlab.com/jeanas/LilyWiki extension] that defines this tag for the wiki, I'll be happy to review it.
:# Scribunto has security implications (e.g., the need to keep Lua updated), so I'd rather only install it if there is a compelling use case for that.
:[[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 21:10, 18 December 2025 (UTC)
::Thank you for your answer. You have a point with security issues, SyntaxHighlight needs Scribunto. There is no special language support for Lilypond anyway, I use Latex, better than nothing. Your installation has to offer proc open, otherwise Scribunto is not working. I have not found a single provider which allows this.
::Maybe I am missing something in my preferences, when editing I do not see anything that supports editing, not even the option to insert links, maybe it's because I don't use the visual editor, I like "pure" editing as it is in Lilypond. CharInsert offers support for Wiki syntax, including tags like <pre>, all combinations of {} and so on.
::Greetings from Austria, [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 03:17, 19 December 2025 (UTC)
:::[off-topic] Where in Austria? Greetings from Kufstein :-) -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:15, 19 December 2025 (UTC)
::::Niederösterreich, nordöstlich von Wien (Bezirk Gänserndorf) [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 15:21, 19 December 2025 (UTC)
:::I don't think SyntaxHighlight needs Scribunto. It uses Pygments, which is a Python (not Lua) library (of which I actually am technically a maintainer, although I've been inactive lately by lack of time). It certainly needs something like <code>exec</code>/<code>proc_open</code>, but this wiki doesn't use a "managed" MediaWiki install (where the provider installs things for you, à la "Wordpress in one click"), it's on a VPS on which I have root access and administrate things myself, so I can install and configure anything (and <code>exec</code> is already being used to run LilyPond). The real problem is that the LilyPond code snippets are mostly added through a the special, non-standard parser tag <code><nowiki><lilypond></nowiki></code> and so the extension I wrote that defines this tag would need to support syntax highlighting.
:::Regarding the editor toolbar, it sounds like what you want is not CharInsert but [https://www.mediawiki.org/wiki/Extension:WikiEditor WikiEditor], which I've just added. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:15, 19 December 2025 (UTC)
::::PS: I also meant to write that Pygments supports LilyPond. (I implemented this a few years ago.) [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 16:26, 19 December 2025 (UTC)
:::::Apropos Pygments: I've submitted a [https://github.com/pygments/pygments/pull/2974 PR] to update LilyPond support some time ago. [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 17:38, 19 December 2025 (UTC)
::::Thank you for installing this extension, this is definitely an improvement. CharInsert is a different animal. Root access is of course best, but you have to do much administration. Usually root access is very expensive when you need a provider. A long time ago I have written a Lilypond extension myself on a home server in my local network.
::::Just in case you are asking who I am, I wrote LSR 1040, 1042, 1043, 1044 (when I remember right) and was involved in 1066 and 1067. [[User:Manuela|Manuela]] ([[User talk:Manuela|talk]]) 19:34, 19 December 2025 (UTC)

== MediaWiki variables for current stable and unstable LilyPond versions ==

Jean,

what do you think about adding [https://www.mediawiki.org/wiki/Manual:Variable MediaWiki variables] that indicate the current stable and unstable LilyPond versions (without the ‘micro’ value)? I suggest

<nowiki>{{LILYSTABLE}}</nowiki> → 2.24
<nowiki>{{LILYDEVEL}}</nowiki> → 2.25

and maybe

<nowiki>{{LILYSTABLEDOC}} → https://lilypond.org/docs/{{LILYSTABLE}}/Documentation</nowiki>
<nowiki>{{LILYDEVELDOC}} → https://lilypond.org/docs/{{LILYDEVEL}}/Documentation</nowiki>

Such variables would reduce maintainance of yet-to-be-written templates. In particular, I would like to add <code><nowiki>Template:convert-ly</nowiki></code>: it would tell users that the snippet in question needs conversion with <code>convert-ly</code> (showing a link to the documentation) for newer versions. -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 05:46, 28 December 2025 (UTC)

:Sounds OK to me. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 08:34, 28 December 2025 (UTC)

User talk:Jean Abou Samra

2025-12-19T16:26:25Z

Jean Abou Samra: /* This wiki has no templates */ Reply

User talk:Jean Abou Samra

2025-12-19T16:15:22Z

Jean Abou Samra: /* This wiki has no templates */ Reply

User talk:Jean Abou Samra

2025-12-18T21:10:27Z

Jean Abou Samra: /* This wiki has no templates */ Reply

User talk:Leonach

2025-12-15T17:23:42Z

Jean Abou Samra:

== Searching with images? ==

Hi all, although i see the reasons for migrating the LSR to this wiki, there is a disadvantage: when searching in the LSR, i could see the images of the scores in the search result, so i could find a possible solution much faster. Is there a way to show images in the search results in this wiki? [[User:Leonach|Leonach]] ([[User talk:Leonach|talk]]) 16:08, 15 December 2025 (UTC)

:@[[User:Jean Abou Samra|Jean]] [https://www.mediawiki.org/w/index.php?title=Project:Support_desk&oldid=8019982#How_to_display_images_in_search_results asked], but the suggested solution doesn't seem to work with SVG images, and there wasn't any further reply. Maybe there is more information available meanwhile -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 16:45, 15 December 2025 (UTC)
::[https://www.mediawiki.org/wiki/Project:Support_desk/Archive_24#How_to_display_images_in_search_results This] is the archived thread with a further reply from MarkAHershberger. Note that the problem is not with SVG per se, but with the fact that the images are directly inlined into the HTML, instead of being stored as files on the server and included with the standard image syntax, which prevents MediaWiki from detecting them as the page thumbnails. The main reason for doing this is that I'm not sure how to purge unused images (e.g., if you preview your changes 20 times before doing an edit, I don't want those 20 images to remain on the server forever).
::At some point, I tried to make it detect those inline images, but it didn't really get anywhere, sorry. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:22, 15 December 2025 (UTC)

User talk:Leonach

2025-12-15T17:22:52Z

Jean Abou Samra: /* Searching with images? */ Reply

== Searching with images? ==

Hi all, although i see the reasons for migrating the LSR to this wiki, there is a disadvantage: when searching in the LSR, i could see the images of the scores in the search result, so i could find a possible solution much faster. Is there a way to show images in the search results in this wiki? [[User:Leonach|Leonach]] ([[User talk:Leonach|talk]]) 16:08, 15 December 2025 (UTC)

:@[[User:Jean Abou Samra|Jean]] [https://www.mediawiki.org/w/index.php?title=Project:Support_desk&oldid=8019982#How_to_display_images_in_search_results asked], but the suggested solution doesn't seem to work with SVG images, and there wasn't any further reply. Maybe there is more information available meanwhile -- [[User:Lemzwerg|Lemzwerg]] ([[User talk:Lemzwerg|talk]]) 16:45, 15 December 2025 (UTC)
::[https://www.mediawiki.org/wiki/Project:Support_desk/Archive_24#How_to_display_images_in_search_results This] is the archived thread with a further reply from MarkAHershberger. Note that the problem is not with SVG per se, but with the fact that the images are directly inlined as HTML, instead of being stored as files on the server and included with the standard image syntax, which prevents MediaWiki from detecting them as the page thumbnails. The main reason for doing this is that I'm not sure how to purge unused images (e.g., if you preview your changes 20 times before doing an edit, I don't want those 20 images to remain on the server forever).
::At some point, I tried to make it detect those inline images, but it didn't really get anywhere, sorry. [[User:Jean Abou Samra|Jean Abou Samra]] ([[User talk:Jean Abou Samra|talk]]) 17:22, 15 December 2025 (UTC)

User talk:Jean Abou Samra

2025-12-13T09:13:07Z

Jean Abou Samra: /* More fonts for the Wiki */ Reply

User talk:Jean Abou Samra

2025-12-12T23:49:48Z

Jean Abou Samra: /* More fonts for the Wiki */ Reply

User talk:Jean Abou Samra

2025-12-12T18:34:23Z

Jean Abou Samra: /* More fonts for the Wiki */ Reply