Re: Emacs Mode Problem with includes

[David Zelinsky]

On Mon, Nov 13, 2023 at 02:45:26PM +1100, Laurie Savage wrote:
>I store my Includes file in a directory ~/Lilypond/includes but
>Lilypond mode cannot locate them even if I specify a full file name e.g
>\include
>"/home/Laurie/Lilypond/includes/jazzchords.ily"
>I set this in my ~/.emacs file
>(custom-set-variables
> '(LilyPond-include-path "/home/laurie/Lilypond/includes")
> '(LilyPond-lilypond-command "/usr/bin/lilypond"))
>Still I get errors like this:
>/home/laurie/Documents/Charts/Transpositions/Dear Old
>Stockholm/Dear-Old-Stockhom_Traditional.ly:3:10: error: cannot find
>file: `/home/Laurie/Lilypond/includes/jazzchords.ily'
>(search path: `/home/laurie/Documents/Charts/Transpositions/Dear Old
>Stockholm:/usr/share/lilypond/2.25.4/ly:/usr/share/lilypond/2.25.4/ps:/
>usr/share/lilypond/2.25.4/scm:/usr/share/lilypond/2.25.4/fonts/otf/:/us
>r/share/lilypond/2.25.4/fonts/svg/:')

I've never used this feature of LilyPond mode, and don't know why it seems not 
to register in the search path.  But I noticed your absolute path in the 
\include starts with "/home/Laurie/" but the search path setting has 
"/home/laurie".  Directory names are case sensitive, and home directories are 
usually lower case, so I suspect "/home/Laurie/" is a typo.

-David

Emacs Mode Problem with includes

[Laurie Savage]

Hi,

I thought I'd give the Emacs Lilypond mode a try-out. I like Emacs and have
used it a lot for coding and writing in LaTeX in my past career. (No editor
wars please, VIM is good too but I'm less familiar with it!)

I store my Includes file in a directory ~/Lilypond/includes but Lilypond
mode cannot locate them even if I specify a full file name e.g \include
"/home/Laurie/Lilypond/includes/jazzchords.ily"

I set this in my ~/.emacs file
(custom-set-variables
 '(LilyPond-include-path "/home/laurie/Lilypond/includes")
 '(LilyPond-lilypond-command "/usr/bin/lilypond"))

Still I get errors like this:
/home/laurie/Documents/Charts/Transpositions/Dear Old
Stockholm/Dear-Old-Stockhom_Traditional.ly:3:10: error: cannot find file:
`/home/Laurie/Lilypond/includes/jazzchords.ily'
(search path: `/home/laurie/Documents/Charts/Transpositions/Dear Old
Stockholm:/usr/share/lilypond/2.25.4/ly:/usr/share/lilypond/2.25.4/ps:/usr/share/lilypond/2.25.4/scm:/usr/share/lilypond/2.25.4/fonts/otf/:/usr/share/lilypond/2.25.4/fonts/svg/:')
\include
 "/home/Laurie/Lilypond/includes/jazzchords.ily"

Any ideas?

Laurie Savage
https://www.queensofthewest.com/

Re: petrucci style notehead for MetronomeMark, plus Piae Cantiones style G clef and time signature

[Jon Arnold]

I'm into this!

1) Not sure on this one- you need to override the notehead in a \note {2}
markup somehow since there's not a dedicated glyph for that.
2) I think that's as close as you get with Emmantaler. You can see the list
of clefs here:
https://lilypond.org/doc/v2.24/Documentation/notation/clef-style
3) \override Staff.TimeSignature.style = #'single-digit

Hope I don't annoy you by adding other things but:
1) there are two semibreve (quarter note in your edition) rests at the
beginning of the line if you haven't seen them
2) consider adding the custos engraver to your staff context like you did
with the ambitus: \consists "Custos_engraver" \override Custos.style =
#'mensural

On Sun, Nov 12, 2023 at 5:24 PM Jeff Olson  wrote:

> This is my first time using quasi-mensural notation for modern notation
> readers (going for medieval look, not historical accuracy).
>
> If you haven't gagged at that, I'd like some help on a few items.
>
> Here's how the original starts ... (IMSLP260656 p48)
> [image: InDulciJubilo1910]
>
> And this is my approximation so far (using more familiar note durations)
> ...
> [image: MWE-mensural.png]
>
> My MWE-mensural.ly so far ... (constrained to overrides in my Voice
> variable vs new MensuralStaff)
>
> \version "2.24.0"
> vexDUMa = \transpose c c' {
>   \tempo 2=100
>   \time 6/8
>   \override Staff.TimeSignature.style = #'mensural
>   \clef "petrucci-g"
>   \override NoteHead.style = #'petrucci
>   \override Staff.MetronomeMark.style = #'petrucci
>   \override Staff.AmbitusNoteHead.style = #'petrucci
>   \cadenzaOn
>   c4\(  c2 c4 e2 f4   g2 a4 g2\) \bar "," %1
>   g4\(  c2 c4 e2 f4   g2 a4 g2.\) \breathe \bar "," %2
>   \bar "||"
> }
> \score {
>   { \vexDUMa }
>   \layout { \context { \Staff \consists "Ambitus_engraver" }}
> }
>
> My questions ...
>
> 1)  How to get petrucci style note head in the tempo indication?
>
> 2)  Where to get the G clef as used in Piae Cantiones?
>
> 3)  How to get the time signature as used in Piae Cantiones?
>
> TIA,
> Jeff
>
>
>
>

Re: Is there a simple way to append markup to a chordname in chordmode?

[Kevin Cole]

On Sun, Nov 12, 2023 at 6:01 AM Robin Bannister  wrote:
> Kevin Cole wrote:
>
> > I would like to use F. Bb and Am as the "real" chords and append "(C)",
> > "(F)" and "(Em)" as text.
>
> This may help:
> https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00416.html
>
> Cheers,
> Robin

Thanks! Following that thread, the winning solution for me was
Jean Abou Samra's response (Mon, 28 Nov 2022 01:22:04 +0100)

https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00425.html

petrucci style notehead for MetronomeMark, plus Piae Cantiones style G clef and time signature

[Jeff Olson]

This is my first time using quasi-mensural notation for modern notation 
readers (going for medieval look, not historical accuracy).


If you haven't gagged at that, I'd like some help on a few items.

Here's how the original starts ... (IMSLP260656 p48)

InDulciJubilo1910

And this is my approximation so far (using more familiar note durations) ...

MWE-mensural.png

My MWE-mensural.ly so far ... (constrained to overrides in my Voice 
variable vs new MensuralStaff)


\version "2.24.0"
vexDUMa = \transpose c c' {
  \tempo 2=100
  \time 6/8
  \override Staff.TimeSignature.style = #'mensural
  \clef "petrucci-g"
  \override NoteHead.style = #'petrucci
  \override Staff.MetronomeMark.style = #'petrucci
  \override Staff.AmbitusNoteHead.style = #'petrucci
  \cadenzaOn
  c4\(  c2 c4 e2 f4   g2 a4 g2\) \bar "," %1
  g4\(  c2 c4 e2 f4   g2 a4 g2.\) \breathe \bar "," %2
  \bar "||"
}
\score {
  { \vexDUMa }
  \layout { \context { \Staff \consists "Ambitus_engraver" }}
}

My questions ...

1)  How to get petrucci style note head in the tempo indication?

2)  Where to get the G clef as used in Piae Cantiones?

3)  How to get the time signature as used in Piae Cantiones?

TIA,
Jeff


\version "2.24.0"
vexDUMa = \transpose c c' {
  \tempo 2=100
  \time 6/8
  \override Staff.TimeSignature.style = #'mensural
  \clef "petrucci-g"
  \override NoteHead.style = #'petrucci
  \override Staff.MetronomeMark.style = #'petrucci
  \override Staff.AmbitusNoteHead.style = #'petrucci
  \cadenzaOn
  c4\(  c2 c4 e2 f4   g2 a4 g2\) \bar "," %1
  g4\(  c2 c4 e2 f4   g2 a4 g2.\) \breathe \bar "," %2
  \bar "||"
}
\score { 
  { \vexDUMa }
  \layout { \context { \Staff \consists "Ambitus_engraver" }}
}

Re: LilyPond 2.25.10

[Peter Crighton]

On Sun, 12 Nov 2023 at 22:08, Jean Abou Samra  wrote:

> Is there a way to quickly see at a glance the changes in a new version? I
> know there is https://lilypond.org/doc/v2.25/Documentation/changes/index and
> although the listing in categories surely has its upsides, I preferred the
> old method of just listing it all in reverse chronological order, which
> made it very easy to just see what changed compared to the prior version
> (if you took a look at it with every release).
>
>
>
> If you're not afraid of the ugly guts of how software is made, you can
> look at
>
>
> https://gitlab.com/lilypond/lilypond/-/commits/master/Documentation/en/changes.tely?ref_type=heads
>
> which is the chronological list of changes affecting the source code of
> the Changes document.
>

Thanks for the link, that suits me quite well! I didn’t know that there was
a repository on GitLab. https://lilypond.org/development.html links to
https://git.savannah.gnu.org/gitweb/?p=lilypond.git … which is neither
really nice to look at nor easy to use (at least for me), but I’m familiar
with GitLab.

Thanks,
Peter

--
Peter Crighton | Musician & Music Engraver based in Mainz, Germany
https://www.petercrighton.de

>

Re: LilyPond 2.25.10 with Guile 3.0

[Jean Abou Samra]

> “_” needs to be replaced with “G_”. Already in Guile 2, but Guile 3 checks for
> it more eagerly.


Fixed in LSR.



signature.asc
Description: This is a digitally signed message part

Re: lilypond does not generate pdf - new install on mac os sonoma

[Abe Raher]

Thank you, Jean, that makes sense and will help.

all the best,

Abe


On Sun, Nov 12, 2023 at 12:53 AM Jean Abou Samra  wrote:

> I'm having the same problem.There's already a thread about this:
> https://lists.gnu.org/archive/html/lilypond-user/2023-06/msg00135.html
> Joshua Armenta posted a solution, something to do with Ghostscript, but I
> couldn't make it to work.
>
> That thread is not about the same problem as this thread.
>
> Your specific Ghostscript error is
>
> Error: /undefined in finddevice
>
> The problem is that recently, Ghostscript (the software used by LilyPond
> to convert its PostScript output to PDF) had a “security fix release”,
> version 10.02.1, which removed a function that was used by LilyPond
> (apparently because it was somehow found to be insecure). See issue 6675
> .
>
> Since security fix releases are always assumed not to break anything,
> packagers pick them up without much thought. In this case, Homebrew was
> quick to upgrade to 10.02.1 and LilyPond broke.
>
> LilyPond has already been changed to avoid using it, but Homebrew doesn't
> have that fix yet.
>
> I don't know enough about Homebrew to say whether it's possible to
> downgrade Ghostscript to 10.02.0. You could try the official binaries
> , which do work.
>
> Best,
>
> Jean
>

Re: LilyPond 2.25.10

[Jean Abou Samra]

> Is there a way to quickly see at a glance the changes in a new version? I know
> there is https://lilypond.org/doc/v2.25/Documentation/changes/index and
> although the listing in categories surely has its upsides, I preferred the old
> method of just listing it all in reverse chronological order, which made it
> very easy to just see what changed compared to the prior version (if you took
> a look at it with every release).


If you're not afraid of the ugly guts of how software is made, you can look at

https://gitlab.com/lilypond/lilypond/-/commits/master/Documentation/en/changes.tely?ref_type=heads

which is the chronological list of changes affecting the source code of the
Changes document.

Best,
Jean




signature.asc
Description: This is a digitally signed message part

Re: LilyPond 2.25.10

[Peter Crighton]

On Sat, 11 Nov 2023 at 19:38, Jonas Hahnfeld via LilyPond user discussion <
lilypond-user@gnu.org> wrote:

> We are happy to announce the release of LilyPond 2.25.10. This is
> termed a development release, but these are usually reliable for
> testing new features and recent bug fixes. However, if you require
> stability, we recommend using version 2.24.2, the current stable
> release.
> Please refer to the Installing section in the Learning Manual for
> instructions how to set up the provided binaries:
> https://lilypond.org/doc/v2.25/Documentation/learning/installing


Is there a way to quickly see at a glance the changes in a new version? I
know there is https://lilypond.org/doc/v2.25/Documentation/changes/index
and although the listing in categories surely has its upsides, I preferred
the old method of just listing it all in reverse chronological order, which
made it very easy to just see what changed compared to the prior version
(if you took a look at it with every release).

Cheers,
Peter

--
Peter Crighton | Musician & Music Engraver based in Mainz, Germany
https://www.petercrighton.de

Re: LilyPond 2.25.10 with Guile 3.0

[Jean Abou Samra]

> Le 12 nov. 2023 à 19:14, Robin Bannister  a écrit :
> 
> If I take the code of LSR1098 [1] , without the demo part,
> Guile3 errors the input-warning call:
> 
> GNU LilyPond 2.25.10 (running Guile 3.0)
> Processing `1.ly'
> Parsing...
> 1.ly:38:2: error: Guile signaled an error for the expression beginning here
> #
> (define-music-function (name-tweaks left-indent right-indent)
> 
> Syntax error:
> 1.ly:40:64: _: bad use of '_' syntactic keyword in subform (_ " pseudoIndents 
> ~s ~s is stretching staff; expect distorted layout") of (_ " pseudoIndents ~s 
> ~s is stretching staff; expect distorted layout")


“_” needs to be replaced with “G_”. Already in Guile 2, but Guile 3 checks for 
it more eagerly.

Re: Fermata Markup below Staff

[Mats Bengtsson]

  
  


On 2023-11-12 17:37, Michael Werner
  wrote:


  
  
Hi Johannes,


  On Sun, Nov 12, 2023 at
11:01 AM Johannes Roeßler 
wrote:
  
  

  Hi all,
  I managed to place a fermata above a barline, I even
managed to place it correctly at the end of the line,
but now I would like to place a fermata sign below the
barline (and rotate it 180°) too (in the bassvoice of a
choir staff group) - simplified example:
  \version "2.24.0"
\relative c' { 
e1 \break \once \override
Score.RehearsalMark.break-visibility =
#end-of-line-visible \mark \markup { \musicglyph
#"scripts.ufermata" } \bar "||" e2
}

  
  
  
  There's a code snippet in the Notation Reference that
does this.  It's at the bottom of:
  http://lilypond.org/doc/v2.24/Documentation/notation/writing-rests#caesuras
  
  

  

That seems like a very clumsy solution, now that \textMark is
  available, but it took me some time to figure out how to convince
  LilyPond to center the mark horizontally on the bar line:
\version "2.24.0"

% Based on \textEndMark, to place it at the end of the line, at
  line breaks:
  textCenteredMark = \tweak self-alignment-X #CENTER \textEndMark
  \etc 
  
  \fixed c' {
  c4 d e f |
  \textCenteredMark\markup\musicglyph #"scripts.ufermata" 
  \tweak direction #DOWN \textCenteredMark\markup\musicglyph
  #"scripts.dfermata"
  f e d c |}
   /Mats


  

Re: LilyPond 2.25.10 with Guile 3.0

[Robin Bannister]

Jonas Hahnfeld wrote:

On Sat, 2023-11-11 at 19:37 +0100, Jonas Hahnfeld wrote:

We are happy to announce the release of LilyPond 2.25.10.


And here are the binaries with Guile 3.0, built using
https://gitlab.com/lilypond/lilypond/-/merge_requests/2163 and
https://gitlab.com/lilypond/lilypond/-/merge_requests/2170 :
https://gitlab.com/lilypond/lilypond/-/packages/20197593

If you have some time, please test them in your setups and report back
in case of problems!



If I take the code of LSR1098 [1] , without the demo part,
Guile3 errors the input-warning call:

GNU LilyPond 2.25.10 (running Guile 3.0)
Processing `1.ly'
Parsing...
1.ly:38:2: error: Guile signaled an error for the expression beginning here
#
 (define-music-function (name-tweaks left-indent right-indent)

Syntax error:
1.ly:40:64: _: bad use of '_' syntactic keyword in subform (_ " 
pseudoIndents ~s ~s is stretching staff; expect distorted layout") of (_ 
" pseudoIndents ~s ~s is stretching staff; expect distorted layout")

1.ly:1: warning: no \version statement found, please add

\version "2.25.10"

for future compatibility
fatal error: failed files: "1.ly"


If I include the rest of the file, I get a lot more errors.


[1] https://lsr.di.unimi.it/LSR/Item?id=1098


Cheers,
Robin

Re: Fermata Markup below Staff

[Johannes Roeßler]

this works perfectly, Michael, saved it to my snippets :)
thx again!
J

upFermata = {
  \once \set Staff.caesuraType = #'((underlying-bar-line . "||"))
  \once \set Staff.caesuraTypeTransform = ##f
  \caesura ^\fermata
}

downFermata = {
  \once \set Staff.caesuraType = #'((underlying-bar-line . "||"))
  \once \set Staff.caesuraTypeTransform = ##f
  \caesura _\fermata
}

musicA = {
  f'1 \upFermata
  R1
  f'2 \upFermata f'2
  R1
  b'1 \upFermata \fine
}

musicB = {
  f'1 \downFermata
  R1
  f'2 \downFermata f'2
  R1
  b'1 \downFermata \fine
}

\new ChoirStaff <<
  \new Staff \musicA
  \new Staff \musicB
>>

Re: Fermata Markup below Staff

[Michael Werner]

Hi Johannes,

On Sun, Nov 12, 2023 at 11:44 AM Johannes Roeßler  wrote:

> Hi Michael,
>
> doesn't work well with a choirstaff though..
>

No, it doesn't, does it.  I missed the part in your original post where you
mentioned the choir staff bit. With a GrandStaff the span bar counts as a
single bar line, which you won't have in a ChoirStaff. So what we want
(maybe?) is something that'll put the fermata above the bar line in the
upper staff, and below the bar line in the lower staff. Am I understanding
correctly that's what you're after? If so, try:

upFermata = {
  \once \set Staff.caesuraType = #'((underlying-bar-line . "||"))
  \once \set Staff.caesuraTypeTransform = ##f
  \caesura ^\fermata
}

downFermata = {
  \once \set Staff.caesuraType = #'((underlying-bar-line . "||"))
  \once \set Staff.caesuraTypeTransform = ##f
  \caesura _\fermata
}

musicA = {
  f'1 \upFermata
  R1
  f'2 \upFermata f'2
  R1
  b'1 \upFermata \fine
}

musicB = {
  f'1 \downFermata
  R1
  f'2 \downFermata f'2
  R1
  b'1 \downFermata \fine
}

\new ChoirStaff <<
  \new Staff \musicA
  \new Staff \musicB
>>

Maybe that'll get a little closer to what you're after.
-- 
Michael

Re: Fermata Markup below Staff

[Johannes Roeßler]

Hi Michael,

doesn't work well with a choirstaff though..

twoWayFermata = {
  \once \set Staff.caesuraType = #'((underlying-bar-line . "||"))
  \once \set Staff.caesuraTypeTransform = ##f
  \caesura ^\fermata _\fermata
}

music = {
  f'1 \twoWayFermata
  R1
  f'2 \twoWayFermata f'2
  R1
  b'1 \twoWayFermata \fine
}

\new ChoirStaff <<
  \new Staff \music
  \new Staff \music
>>
Best, Johannes

Hi Johannes,

On Sun, Nov 12, 2023 at 11:01 AM Johannes Roeßler  wrote:

Hi all,

I managed to place a fermata above a barline, I even managed to
place it correctly at the end of the line, but now I would like to
place a fermata sign below the barline (and rotate it 180°) too
(in the bassvoice of a choir staff group) - simplified example:

\version "2.24.0"
\relative c' {
e1 \break \once \override Score.RehearsalMark.break-visibility =
#end-of-line-visible \mark \markup { \musicglyph
#"scripts.ufermata" } \bar "||" e2
}


There's a code snippet in the Notation Reference that does this.  It's 
at the bottom of:

http://lilypond.org/doc/v2.24/Documentation/notation/writing-rests#caesuras
 --
Michael

Re: Fermata Markup below Staff

[Johannes Roeßler]

ah, even more elegant - didn't find it during my search... thx, Michael!

Hi Johannes,

On Sun, Nov 12, 2023 at 11:01 AM Johannes Roeßler  wrote:

Hi all,

I managed to place a fermata above a barline, I even managed to
place it correctly at the end of the line, but now I would like to
place a fermata sign below the barline (and rotate it 180°) too
(in the bassvoice of a choir staff group) - simplified example:

\version "2.24.0"
\relative c' {
e1 \break \once \override Score.RehearsalMark.break-visibility =
#end-of-line-visible \mark \markup { \musicglyph
#"scripts.ufermata" } \bar "||" e2
}


There's a code snippet in the Notation Reference that does this.  It's 
at the bottom of:

http://lilypond.org/doc/v2.24/Documentation/notation/writing-rests#caesuras
 --
Michael

Re: Fermata Markup below Staff

[Michael Werner]

Hi Johannes,

On Sun, Nov 12, 2023 at 11:01 AM Johannes Roeßler  wrote:

> Hi all,
>
> I managed to place a fermata above a barline, I even managed to place it
> correctly at the end of the line, but now I would like to place a fermata
> sign below the barline (and rotate it 180°) too (in the bassvoice of a
> choir staff group) - simplified example:
>
> \version "2.24.0"
> \relative c' {
> e1 \break \once \override Score.RehearsalMark.break-visibility =
> #end-of-line-visible \mark \markup { \musicglyph #"scripts.ufermata" } \bar
> "||" e2
> }
>

There's a code snippet in the Notation Reference that does this.  It's at
the bottom of:
http://lilypond.org/doc/v2.24/Documentation/notation/writing-rests#caesuras
 --
Michael

Re: Fermata Markup below Staff

[William Rehwinkel via LilyPond user discussion]

I see, thanks for the update.

I found a solution to this problem here: 
https://www.reddit.com/r/lilypond/comments/vozo9z/comment/ieibg4j/ does 
this do what you were hoping for?


-William

Pasted below in-case this link goes away...

\version "2.25.7"

\score {
\new PianoStaff
<<
\new Staff = "upper"
\relative c' {
c1
c
}

\new Staff = "lower" \with { \consists "Mark_engraver" }
\relative c' {
\override Staff.RehearsalMark.direction = #DOWN
\override Staff.RehearsalMark.rotation = #'(180 0 0)
c1
\mark \markup { \smaller \smaller \musicglyph 
#"scripts.ufermata" }

c
}
>>
}


On 11/12/23 11:20, Johannes Roeßler wrote:

Am 12.11.2023 um 17:10 schrieb William Rehwinkel:

\relative c' {
e1 \break \once \override Score.RehearsalMark.break-visibility = 
#end-of-line-visible \tweak direction #DOWN \mark \markup { 
\musicglyph #"scripts.dfermata" } \bar "||" e2
} 


thx William for the quick response, always an amazing group...

works for one fermata - but in my context (up in soprano, down in bass) 
it gives a warning "conflict with event: `ad-hoc-mark-event'" and only 
produces the first one:


\version "2.24.0"

\score {
   \new StaffGroup <<
  \new Staff {
    e1 \break \once \override Score.RehearsalMark.break-visibility = 
#end-of-line-visible \mark \markup { \musicglyph #"scripts.ufermata" } 
\bar "||" e2

  }
  \new Staff {
     e1 \break \once \override Score.RehearsalMark.break-visibility 
= #end-of-line-visible \tweak direction #DOWN \mark \markup { 
\musicglyph #"scripts.dfermata" }

     \bar "||" e2
  }
   >>
   \layout {

   }
}



--
William Rehwinkel - Oberlin College and Conservatory '24

will...@williamrehwinkel.net

PGP key: https://ftp.williamrehwinkel.net/pubkey.txt


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Fermata Markup below Staff

[Johannes Roeßler]

Am 12.11.2023 um 17:10 schrieb William Rehwinkel:

\relative c' {
e1 \break \once \override Score.RehearsalMark.break-visibility = 
#end-of-line-visible \tweak direction #DOWN \mark \markup { 
\musicglyph #"scripts.dfermata" } \bar "||" e2
} 


thx William for the quick response, always an amazing group...

works for one fermata - but in my context (up in soprano, down in bass) 
it gives a warning "conflict with event: `ad-hoc-mark-event'" and only 
produces the first one:


\version "2.24.0"

\score {
  \new StaffGroup <<
 \new Staff {
   e1 \break \once \override Score.RehearsalMark.break-visibility = 
#end-of-line-visible \mark \markup { \musicglyph #"scripts.ufermata" } 
\bar "||" e2

 }
 \new Staff {
    e1 \break \once \override Score.RehearsalMark.break-visibility 
= #end-of-line-visible \tweak direction #DOWN \mark \markup { 
\musicglyph #"scripts.dfermata" }

    \bar "||" e2
 }
  >>
  \layout {

  }
}

Re: Fermata Markup below Staff

[William Rehwinkel via LilyPond user discussion]

Dear Johannes,

If you change "ufermata" to "dfermata" and insert "\tweak direction 
#DOWN" before "\mark" that should get you what you want.


Thanks,
-William

\version "2.24.0"
\relative c' {
e1 \break \once \override Score.RehearsalMark.break-visibility = 
#end-of-line-visible \tweak direction #DOWN \mark \markup { \musicglyph 
#"scripts.dfermata" } \bar "||" e2

}


On 11/12/23 11:00, Johannes Roeßler wrote:

Hi all,

I managed to place a fermata above a barline, I even managed to place it 
correctly at the end of the line, but now I would like to place a 
fermata sign below the barline (and rotate it 180°) too (in the 
bassvoice of a choir staff group) - simplified example:


\version "2.24.0"
\relative c' {
e1 \break \once \override Score.RehearsalMark.break-visibility = 
#end-of-line-visible \mark \markup { \musicglyph #"scripts.ufermata" } 
\bar "||" e2

}

What do I need to do?

Best Johannes




--
William Rehwinkel - Oberlin College and Conservatory '24

will...@williamrehwinkel.net

PGP key: https://ftp.williamrehwinkel.net/pubkey.txt


OpenPGP_signature.asc
Description: OpenPGP digital signature

Fermata Markup below Staff

[Johannes Roeßler]

Hi all,

I managed to place a fermata above a barline, I even managed to place it 
correctly at the end of the line, but now I would like to place a 
fermata sign below the barline (and rotate it 180°) too (in the 
bassvoice of a choir staff group) - simplified example:


\version "2.24.0"
\relative c' {
e1 \break \once \override Score.RehearsalMark.break-visibility = 
#end-of-line-visible \mark \markup { \musicglyph #"scripts.ufermata" } 
\bar "||" e2

}

What do I need to do?

Best Johannes

Re: top-level `\midi` doesn't work as expected

[Mats Bengtsson]

  
  
On 2023-11-12 14:31, Werner LEMBERG
  wrote:


  

  
MIDI settings can be changed globally (or in a book or bookpart), but
the generation of an actual MIDI file is only triggered when a \midi
block is encountered inside of a \score .

  
  
Thanks for the idea and wording.

  https://gitlab.com/lilypond/lilypond/-/merge_requests/2171


Would it be possible to reformulate a bit to make it even more
  clear that this is analogous to how \layout blocks behave (the
  only difference being that a \score block that contains nor a
  layout neither a midi block implicitly contains a layout block).
  For example:
A @code{@bs{}midi} block at the top level can be used to change
  MIDI settings globally; however, the generation of an actual MIDI
  file only happens when a @code{@bs{}midi} block is part of a
  @code{@bs{}score} block. Similarly, a @code{@bs{}layout} block
  at the top level affect layout settings globally, but does not
  influence
  if printed output is produced or not.
   /Mats

  

Re: pageNumber

[bobr...@centrum.is]

Thanks Micheal!

The '\unless \on-first-page' was what I went with on the first try.  It was the 
magic sauce.

-David

- Original Message -
> From: "Michael Werner" 
> To: "bobroff" 
> Cc: "Lillypond Users Mailing List" 
> Sent: Sunday, November 12, 2023 1:09:05 PM
> Subject: Re: pageNumber

> Hi David,
> 
> On Sun, Nov 12, 2023 at 7:18 AM bobr...@centrum.is 
> wrote:
> 
>> I have the following in my \paper block.  I want to eliminate the page
>> number on page 1.  I have 'print-first-page-number = ##f' but the
>> oddHeaderMarkup is overriding it.  Is there a way around this? Some sort of
>> conditional?
>>
> 
> Turns out you just need to swap two lines. The \if conditional will apply
> to the next item ... and just the next item. It prints the next item if
> true, and leaves it blank if false. But the next item is the empty quotes,
> so something that's already empty. So just swap the \if conditional line
> down one to put it right before the page number line and all should be well.
> 
>  oddHeaderMarkup = \markup {
>\fill-line {
>  "" \larger\bold "SCORE"
>  \if \should-print-page-number
>  \fromproperty #'page:page-number-string
>}
>  }
> 
> There's also an alternative you can use, that kind of does this from the
> opposite viewpoint. This will print the page number unless it's the first
> page. Either should work, just going at things in two different ways. In
> some circumstances (special cases? tricky layouts?) one might be preferable
> over the other. But there are options to explore.
> 
>  oddHeaderMarkup = \markup {
>\fill-line {
>  "" \larger\bold "SCORE"
>  \unless \on-first-page
>  \fromproperty #'page:page-number-string
>}
>  }
> 
> For more details on these, have a look at:
> http://lilypond.org/doc/v2.25/Documentation/notation/custom-layout-for-headers-and-footers
> and
> http://lilypond.org/doc/v2.25/Documentation/notation/conditional-markup
> --
> Michael

Re: Score layout - ragged bottom and page break?

[Alasdair McAndrew]

Thanks, Michael - that looks like the perfect answer.  Typical of me, I
seem to have explored every page in the documentation except for that one.

Thanks again,
Alasdair

On Mon, 13 Nov 2023, 1:04 am Michael Werner,  wrote:

> Hi Alasdair,
>
> On Sun, Nov 12, 2023 at 8:47 AM Alasdair McAndrew 
> wrote:
> 
>
>> How can I force each score with a book to have a last ragged bottom, and
>> each score beginning on a new page?
>>
>
> Might try putting each score into a \bookpart section. When I put multiple
> scores into a single PDF that's how I go about it - works quite well for
> me. Something like:
>
> \paper {
>   ::global paper settings ::
> }
>
> \book {
>   \bookpart {
> \paper {
>:: paper settings for just this score ::
> }
> \score {
>   :: the score ::
> }
>   }
>   \bookpart {
> :: and the next score, and so forth ::
>   }
> }
>
> One note - using \bookpart inserts a page break between parts, so no need
> for any explicit \pageBreak commands. For some more details have a look at:
>
> http://lilypond.org/doc/v2.24/Documentation/notation/multiple-scores-in-a-book
> --
> Michael
>
>

Re: Score layout - ragged bottom and page break?

[Michael Werner]

Hi Alasdair,

On Sun, Nov 12, 2023 at 8:47 AM Alasdair McAndrew  wrote:


> How can I force each score with a book to have a last ragged bottom, and
> each score beginning on a new page?
>

Might try putting each score into a \bookpart section. When I put multiple
scores into a single PDF that's how I go about it - works quite well for
me. Something like:

\paper {
  ::global paper settings ::
}

\book {
  \bookpart {
\paper {
   :: paper settings for just this score ::
}
\score {
  :: the score ::
}
  }
  \bookpart {
:: and the next score, and so forth ::
  }
}

One note - using \bookpart inserts a page break between parts, so no need
for any explicit \pageBreak commands. For some more details have a look at:
http://lilypond.org/doc/v2.24/Documentation/notation/multiple-scores-in-a-book
-- 
Michael

Score layout - ragged bottom and page break?

[Alasdair McAndrew]

Hello,

(Note: Lilypond v. 2.24.2, in Linux.)

I am setting a group of pieces; each piece is in its own score block.  I
want each score to start on a new page, and the final page in each score to
have a ragged-last-bottom, so that the systems are evenly spaced - these
are duets, and I like no more than 6 systems per a4 page.

I am managing this so far by having a pageBreak command between each score
block.

The trouble is that this seems to have the effect of filling each page
equally, and overriding the system-system-spacing variables I've set in the
paper block.

The only score which is properly set is the last one, which is not followed
by a pageBreak command.

I've tried putting "ragged-last-bottom = ##t" in the global layout block,
and in the layout block within a score, but it makes no difference.

How can I force each score with a book to have a last ragged bottom, and
each score beginning on a new page?

Many thanks,
Alasdair
-- 
Alasdair McAndrew (he/him)
mob: 0432 854 858

https://numbersandshapes.net

Re: top-level `\midi` doesn't work as expected

[Werner LEMBERG]

> MIDI settings can be changed globally (or in a book or bookpart), but
> the generation of an actual MIDI file is only triggered when a \midi
> block is encountered inside of a \score .

Thanks for the idea and wording.

  https://gitlab.com/lilypond/lilypond/-/merge_requests/2171


  Werner

Re: pageNumber

[Michael Werner]

Hi David,

On Sun, Nov 12, 2023 at 7:18 AM bobr...@centrum.is 
wrote:

> I have the following in my \paper block.  I want to eliminate the page
> number on page 1.  I have 'print-first-page-number = ##f' but the
> oddHeaderMarkup is overriding it.  Is there a way around this? Some sort of
> conditional?
>

Turns out you just need to swap two lines. The \if conditional will apply
to the next item ... and just the next item. It prints the next item if
true, and leaves it blank if false. But the next item is the empty quotes,
so something that's already empty. So just swap the \if conditional line
down one to put it right before the page number line and all should be well.

  oddHeaderMarkup = \markup {
\fill-line {
  "" \larger\bold "SCORE"
  \if \should-print-page-number
  \fromproperty #'page:page-number-string
}
  }

There's also an alternative you can use, that kind of does this from the
opposite viewpoint. This will print the page number unless it's the first
page. Either should work, just going at things in two different ways. In
some circumstances (special cases? tricky layouts?) one might be preferable
over the other. But there are options to explore.

  oddHeaderMarkup = \markup {
\fill-line {
  "" \larger\bold "SCORE"
  \unless \on-first-page
  \fromproperty #'page:page-number-string
}
  }

For more details on these, have a look at:
http://lilypond.org/doc/v2.25/Documentation/notation/custom-layout-for-headers-and-footers
and
http://lilypond.org/doc/v2.25/Documentation/notation/conditional-markup
-- 
Michael

LilyPond 2.25.10 with Guile 3.0

[Jonas Hahnfeld via LilyPond user discussion]

On Sat, 2023-11-11 at 19:37 +0100, Jonas Hahnfeld wrote:
> We are happy to announce the release of LilyPond 2.25.10.

And here are the binaries with Guile 3.0, built using
https://gitlab.com/lilypond/lilypond/-/merge_requests/2163 and
https://gitlab.com/lilypond/lilypond/-/merge_requests/2170 :
https://gitlab.com/lilypond/lilypond/-/packages/20197593

If you have some time, please test them in your setups and report back
in case of problems!

Jonas


signature.asc
Description: This is a digitally signed message part

Re: top-level `\midi` doesn't work as expected

[David Kastrup]

Werner LEMBERG  writes:

> +A @code{@bs{}midi} block outside of @code{@bs{}score} does
> +@emph{not} create a MIDI file.}

MIDI settings can be changed globally (or in a book or bookpart), but
the generation of an actual MIDI file is only triggered when a \midi
block is encountered inside of a \score .

Something like that.  It doesn't help the user as much when you tell
them what doesn't create a MIDI file: after all, they will rather be
looking at how to create one.

-- 
David Kastrup

pageNumber

[bobr...@centrum.is]

I have the following in my \paper block.  I want to eliminate the page number 
on page 1.  I have 'print-first-page-number = ##f' but the oddHeaderMarkup is 
overriding it.  Is there a way around this? Some sort of conditional?  

Thanks,

David


\paper {
  print-page-number = ##t
  first-page-number = 1
  print-first-page-number = ##f
  evenHeaderMarkup = \markup {
\fill-line {
  \if \should-print-page-number
  \fromproperty #'page:page-number-string
  \larger\bold "SCORE" ""
}
  }
  oddHeaderMarkup = \markup {
\fill-line {
  \if \should-print-page-number
  "" \larger\bold "SCORE" ""
  \fromproperty #'page:page-number-string
}
  }
}

Re: Is there a simple way to append markup to a chordname in chordmode?

[Robin Bannister]

Kevin Cole wrote:



I would like to use F. Bb and Am as the "real" chords and append "(C)",
"(F)" and "(Em)" as text. 


This may help:
https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00416.html


Cheers,
Robin

Re: top-level `\midi` doesn't work as expected

[Werner LEMBERG]

>  Thanks. I'll add this information to the NR.
> 
> 
> Right now, the NR says the following
> (https://lilypond.org/doc/v2.24/Documentation/notation/the-midi-block.html). 
> What
> do you think needs to be clarified?
> 
>   To create a MIDI output file from a LilyPond input file, insert
>   a\midi block, which can be empty, within the \score block;
> 
>\score {
> … music …
> \layout { }
> \midi { }
>   }

Since it is often not necessary to use `\score` for printed output
explicitly I would like to add the patch below to make it clear that
for MIDI output a `\score` block is mandatory.


Werner

==

diff --git a/Documentation/en/notation/input.itely 
b/Documentation/en/notation/input.itely
index 02621905aa..e6e26f8967 100644
--- a/Documentation/en/notation/input.itely
+++ b/Documentation/en/notation/input.itely
@@ -3830,7 +3830,10 @@ To create a MIDI output file from a LilyPond input file, 
insert a
 @warning{A @code{@bs{}score} block that, as well as the music, contains
 only a @code{@bs{}midi} block (i.e., @emph{without} the
 @code{@bs{}layout} block), will only produce MIDI output files.  No
-notation will be printed.}
+notation will be printed.
+
+A @code{@bs{}midi} block outside of @code{@bs{}score} does
+@emph{not} create a MIDI file.}
 
 The default output file extension (@code{.midi}) can be changed by using
 the @code{-dmidi-extension} option with the @code{lilypond} command:

Re: top-level `\midi` doesn't work as expected

[Jean Abou Samra]

 
 
  
    
   
   
   
Thanks. I'll add this information to the NR.

   
  
    
   
  
   Right now, the NR says the following (https://lilypond.org/doc/v2.24/Documentation/notation/the-midi-block.html). What do you think needs to be clarified?
   
  
    
   
   
   To create a MIDI output file from a LilyPond input file, insert a\midi block, which can be empty, within the \score block; 

\score {
  … music …
  \layout { }
  \midi { }
} 

  
 

Re: using partcombine with different clefs, repeats, text

[Leo Correia de Verdier]

I think this sounds like a use case for a long text preface explaining what is 
to be performed in what order and why, just notating everything on a treble 
clef and doing manual octavations in the midi file. Maybe writing a reminding 
1S,2B: or such (not sure I got it completely right from your explanation) in 
front of each stanza of text. I don’t think the baritone will be too confused.


> 12 nov. 2023 kl. 10:31 skrev N. Andrew Walsh :
> 
> 
> Hi List,
> 
> sigh … here we go again. I apologize in advance for my client, a hobbyist 
> composer who thinks entirely in terms of cutting and pasting, moving things 
> around manually, and not in terms of how to notate anything clearly. Here 
> goes:
> 
> He has a song for soprano, baritone, and piano. The song has four verses, 
> alternating between the two voices (the baritone, weirdly, needs to read a 
> treble clef, so I'm using treble_8 for him). However, he wants to repeat the 
> entire song (ie, enclose the four verses in a '\repeat volta {}' expression), 
> *but* he wants the voices to alternate verses, and the second time through to 
> sing the text in English (first time through is in German; he's in his 
> "Schubert phase."). He wants both voices on a single line.
> 
> So I *could* notate the baritone in the wrong octave and just use the same 
> music for both repeats, but that still leaves me the problem of what to do 
> with the text. And I don't see a good way to do this without having a lot of 
> explanatory text for each verse. This also leaves me the problem of how this 
> is supposed to look in the parts. 
> 
> Do any of you have suggestions for how I might format this so there isn't a 
> lot of explanatory text cluttering up the score?
> 
> Thanks for the help,
> 
> N. Andrew Walsh, PhD, Dr. phil.
> Komponist, Musikwissenschaftler | Composer, Musicologist
> er/ihn/ihm/sein | he/him/his
> Berlin

Re: using partcombine with different clefs, repeats, text

[N. Andrew Walsh]

PS - you know what? I'm sorry: I'm making this guy's work much more
complicated than it needs to be. This is really just a song for single
voice and piano; I'll notate it that way and leave it to him to work out
with the performers who sings which verse in which language. Sorry for the
trouble!

A
er/ihn/ihm/sein | he/him/his
Berlin


On Sun, Nov 12, 2023 at 10:30 AM N. Andrew Walsh 
wrote:

> Hi List,
>
> sigh … here we go again. I apologize in advance for my client, a hobbyist
> composer who thinks entirely in terms of cutting and pasting, moving things
> around manually, and not in terms of how to notate anything clearly. Here
> goes:
>
> He has a song for soprano, baritone, and piano. The song has four verses,
> alternating between the two voices (the baritone, weirdly, needs to read a
> treble clef, so I'm using treble_8 for him). However, he wants to repeat
> the entire song (ie, enclose the four verses in a '\repeat volta {}'
> expression), *but* he wants the voices to alternate verses, and the second
> time through to sing the text in English (first time through is in German;
> he's in his "Schubert phase."). He wants both voices on a single line.
>
> So I *could* notate the baritone in the wrong octave and just use the same
> music for both repeats, but that still leaves me the problem of what to do
> with the text. And I don't see a good way to do this without having a lot
> of explanatory text for each verse. This also leaves me the problem of how
> this is supposed to look in the parts.
>
> Do any of you have suggestions for how I might format this so there isn't
> a lot of explanatory text cluttering up the score?
>
> Thanks for the help,
>
> N. Andrew Walsh, PhD, Dr. phil.
> Komponist, Musikwissenschaftler | Composer, Musicologist
> er/ihn/ihm/sein | he/him/his
> Berlin
>

using partcombine with different clefs, repeats, text

[N. Andrew Walsh]

Hi List,

sigh … here we go again. I apologize in advance for my client, a hobbyist
composer who thinks entirely in terms of cutting and pasting, moving things
around manually, and not in terms of how to notate anything clearly. Here
goes:

He has a song for soprano, baritone, and piano. The song has four verses,
alternating between the two voices (the baritone, weirdly, needs to read a
treble clef, so I'm using treble_8 for him). However, he wants to repeat
the entire song (ie, enclose the four verses in a '\repeat volta {}'
expression), *but* he wants the voices to alternate verses, and the second
time through to sing the text in English (first time through is in German;
he's in his "Schubert phase."). He wants both voices on a single line.

So I *could* notate the baritone in the wrong octave and just use the same
music for both repeats, but that still leaves me the problem of what to do
with the text. And I don't see a good way to do this without having a lot
of explanatory text for each verse. This also leaves me the problem of how
this is supposed to look in the parts.

Do any of you have suggestions for how I might format this so there isn't a
lot of explanatory text cluttering up the score?

Thanks for the help,

N. Andrew Walsh, PhD, Dr. phil.
Komponist, Musikwissenschaftler | Composer, Musicologist
er/ihn/ihm/sein | he/him/his
Berlin

Re: top-level `\midi` doesn't work as expected

[Werner LEMBERG]

>> I wonder whether it is expected that this simple input
>> 
>> ```
>> { c' }
>> \midi{}
>> ```
>> 
>> doesn't create a MIDI file.
> 
> 
> Yes.  [...]

Thanks.  I'll add this information to the NR.


Werner

Re: lilypond does not generate pdf - new install on mac os sonoma

[Jean Abou Samra]

> I'm having the same problem.There's already a thread about this: 
> [https://lists.gnu.org/archive/html/lilypond-user/2023-06/msg00135.html](https://lists.gnu.org/archive/html/lilypond-user/2023-06/msg00135.html)
> Joshua Armenta posted a solution, something to do with Ghostscript, but I 
> couldn't make it to work.

That thread is not about the same problem as this thread.

Your specific Ghostscript error is

```
Error: /undefined in finddevice
```

The problem is that recently, Ghostscript (the software used by LilyPond to 
convert its PostScript output to PDF) had a “security fix release”, version 
10.02.1, which removed a function that was used by LilyPond (apparently because 
it was somehow found to be insecure). See [issue 
6675](https://gitlab.com/lilypond/lilypond/-/issues/6675).

Since security fix releases are always assumed not to break anything, packagers 
pick them up without much thought. In this case, Homebrew was quick to upgrade 
to 10.02.1 and LilyPond broke.

LilyPond has already been changed to avoid using it, but Homebrew doesn't have 
that fix yet.

I don't know enough about Homebrew to say whether it's possible to downgrade 
Ghostscript to 10.02.0. You could try the [official 
binaries](https://lilypond.org/download.html), which do work.

Best,

Jean


signature.asc
Description: This is a digitally signed message part

Re: top-level `\midi` doesn't work as expected

[Jean Abou Samra]

> I wonder whether it is expected that this simple input
> 
> ```
> { c' }
> \midi{}
> ```
> 
> doesn't create a MIDI file.


Yes. Otherwise you could not do

```
\midi { global MIDI settings ... }

fooMusic = ...  
\score { \fooMusic \layout { } }  
\score { \unfoldRepeats \fooMusic \midi { } }

barMusic = ...  
\score { \barMusic \layout { } }  
\score { \unfoldRepeats \barMusic \midi { } }
```


signature.asc
Description: This is a digitally signed message part

Re: lilypond does not generate pdf - new install on mac os sonoma

[Abe Raher]

Thank you Ben and Leonardo!

I tried Joshua Armenta's proposed fix. I don't think it actually changed
anything. I still got the same ghostscript error after I tried the
procedure.

 % cd /usr/local/share/doc

myusername@myhostname % ls -al | grep ghost

lrwxr-xr-x   1 myusername  admin54 Nov 11 15:37 ghostscript ->
../../Cellar/ghostscript/10.02.1/share/doc/ghostscript

myusername@myhostname % sudo chown -R `whoami` ghostscript

Password:

myusername@myhostname % brew link --overwrite ghostscript

Warning: Already linked: /usr/local/Cellar/ghostscript/10.02.1

To relink, run:

  brew unlink ghostscript && brew link ghostscript

Ben, you can see from the above that I am on the latest version, 10.02.1.
What version do you think I should downgrade to? And can that be done with
brew?









On Sat, Nov 11, 2023 at 4:43 PM Ben Bradshaw 
wrote:

> Essentially you need to downgrade ghostscript a version. Although with the
> new release announced today I don't know if it will be fixed or not.
>
> On Sat, Nov 11, 2023, 5:22 PM Leonardo van der Laat 
> wrote:
>
>> I'm having the same problem.
>> There's already a thread about this:
>> https://lists.gnu.org/archive/html/lilypond-user/2023-06/msg00135.html
>> Joshua Armenta posted a solution, something to do with Ghostscript, but I
>> couldn't make it to work.
>>
>> On Sat, Nov 11, 2023 at 5:39 PM Abe Raher  wrote:
>>
>>> hey folks – with my newly installed lilypond on mac os sonoma, lilypond
>>> generates midi but no pdfs
>>>
>>> i've tested a number of .ly files that successfully generated scores
>>> previously – none generate pdfs now
>>>
>>> and i just tested the simplest template in lilypond's docs ... please
>>> have a look at the log output and give me a clue!
>>>
>>> thanks very much
>>>
>>> ***
>>>
>>> what i've got:
>>>
>>> Mac OS: 14.1.1 (23B81)
>>>
>>> % lilypond --version
>>>
>>> GNU LilyPond 2.24.2 (running Guile 3.0)
>>>
>>>
>>>
>>> test file:
>>>
>>>
>>>
>>> melody = \relative c' {
>>>   \clef treble
>>>   \key c \major
>>>   \time 4/4
>>>
>>>   a4 b c d
>>> }
>>>
>>> \score {
>>>   \new Staff \melody
>>>   \layout { }
>>>   \midi { }
>>> }
>>>
>>>
>>>
>>> test command:
>>>
>>>  % lilypond --loglevel=debug template-notes-only.ly
>>>
>>>
>>> ***
>>>
>>>
>>> command output:
>>>
>>>
>>> Log level set to 287
>>> GNU LilyPond 2.24.2 (running Guile 3.0)
>>>
>>> Relocation
>>>   Absolute file name of LilyPond binary computed from PATH:
>>>
>>> PATH=/Library/Frameworks/Python.framework/Versions/3.7/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin
>>> argv0=lilypond
>>>   Setting INSTALLER_PREFIX to '/usr/local/Cellar/lilypond/2.24.2'
>>>   Using run-time value for datadir,
>>> setting it to
>>> '/usr/local/Cellar/lilypond/2.24.2/share/lilypond/2.24.2'
>>>   Using run-time value for libdir,
>>> setting it to '/usr/local/Cellar/lilypond/2.24.2/lib/lilypond/2.24.2'
>>>   Using run-time value for localedir,
>>> setting it to '/usr/local/Cellar/lilypond/2.24.2/share/locale'
>>>   Using compile-time value for relocdir,
>>> setting it to ''
>>>   Prepending '/usr/local/Cellar/lilypond/2.24.2/bin' to PATH
>>>   Setting PATH to
>>> '/usr/local/Cellar/lilypond/2.24.2/bin:/Library/Frameworks/Python.framework/Versions/3.7/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin'
>>> Setting GUILE_AUTO_COMPILE to '0'
>>> Setting GUILE_WARN_DEPRECATED to 'detailed'
>>> Setting XDG_CACHE_HOME to
>>> '/usr/local/Cellar/lilypond/2.24.2/share/lilypond/2.24.2'
>>> Setting GC_INITIAL_HEAP_SIZE to '40M'
>>> Setting GC_NPROCS to '1'
>>> Setting GC_FREE_SPACE_DIVISOR to '1'
>>>
>>>
>>> Effective prefix:
>>> '/usr/local/Cellar/lilypond/2.24.2/share/lilypond/2.24.2'
>>>
>>> PATH="/usr/local/Cellar/lilypond/2.24.2/bin:/Library/Frameworks/Python.framework/Versions/3.7/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin"
>>>
>>>
>>> [/usr/local/Cellar/lilypond/2.24.2/share/lilypond/2.24.2/scm/lily/lily.scm]
>>>
>>> [/usr/local/Cellar/lilypond/2.24.2/share/lilypond/2.24.2/scm/lily/lily-library.scm]
>>>
>>> [/usr/local/Cellar/lilypond/2.24.2/share/lilypond/2.24.2/scm/lily/output-lib.scm]
>>>
>>> [/usr/local/Cellar/lilypo