I just realized that the string order in the lilypond code I previously
included is opposite that of the diagram. As a guitarist ( or non-guitarist),
creating a fret diagram, it is far more intuitive to write the diagram from
first to sixth string since that’s the way the diagram displays everything.
Here is the way I would recommend the example snippets be if I were to have
gotten it right the first time:
\markup {
\vspace #1
\override #'(fret-diagram-details . ((finger-code . below-string)
(dot-radius . 0.3)
(orientation . landscape)
(string-thickness-factor . 0.3)
(top-fret-thickness . 7)
(string-label-font-mag . 0.3))
)
\override #'(size . 2)
\center-column {
“Notes of each String of the Guitar"
\fret-diagram-verbose #'(
(place-fret 1 0 "E" white)(open 1)
(place-fret 2 0 "B" white)(open 2)
(place-fret 3 0 "G" white)(open 3)
(place-fret 4 0 "D" white)(open 4)
(place-fret 5 0 "A" white)(open 5)
(place-fret 6 0 "E" white)(open 6)
)
}
}
> On Jan 29, 2026, at 3:21 AM, Werner LEMBERG <[email protected]> wrote:
>
>
>> The NR link you gave is very good, especially the last two examples,
>> which have the only documentation of inverted and markup as args to
>> place-fret.
>>
>> But those examples are not part of the snippets link [3] that the NR
>> describes as "exhaustive". Neither is the use of "white" as an arg
>> of place-fret. It only shows white as an override to dot-color,
>> where it appears to have an effect more like "inverted" (a circle
>> with white fill as opposed to a complete white out).
>>
>> Trying to find some authoritative definition of place-fret, I first
>> tried the index (no hits) then, in case it was a function, I looked in
>> the IR function list (no hits).
>
> `place-fret` is part of the `\fret-diagram-verbose` markup; the
> documentation you cite is part of the markup's description. Attached
> you can see it how it looks like in the PDF version of the NR.
>
> Can you please explain how and why you missed that? While
> `place-fret` is just a ('named') list as part of the arguments of that
> markup; it is not a function.
>
>> Maybe the snippets examples can be expanded so that they really are
>> exhaustive.
>
> I'm not a guitar player; my knowledge of fret diagrams is essentially
> zero. If you can cook up examples please help! You can contribute
> them easily by adjusting
>
> https://wiki.lilypond.community/wiki/Fret_diagrams_explained_and_developed
>
> The next Wiki import will then update the LilyPond documentation.
>
>> Lilypond's fret diagram code appears to be well-thought-out but still
>> with hidden/implicit capabilities. More examples and index entries
>> would help show off all that great work.
>
> What index entries (and where) do you want me to add?
>
>
> Werner

