> On Jul 8, 2026, at 9:51 AM, Knute Snortum <[email protected]> wrote:
> 
> 
> 
> --
> Knute Snortum
> 
> 
> 
> On Wed, Jul 8, 2026 at 7:42 AM David Kastrup <[email protected] 
> <mailto:[email protected]>> wrote:
>> "[email protected] <mailto:[email protected]>" <[email protected] 
>> <mailto:[email protected]>> writes:
>> 
>> > This morning I have found that charts I could render yesterday without 
>> > problems now fail.  Nothing has changed in the files or my Lilypond 
>> > installation since I last rendered this chart yesterday afternoon.  I have 
>> > no idea what has happened and am probably missing something terribly 
>> > obvious (since that seems to usually be the case).
>> >
>> > FWIW MacOS 26.5.1.
>> >
>> > The log:
>> >
>> > Starting lilypond 2.26.0 [Wassup MWE.ly]...
>> > Processing `/Users/tim/Music/Music Charts/Lilypond Charts/Rock Tunes/Just 
>> > The Two Of US/Wassup MWE.ly'
>> > Parsing...
>> > /Users/tim/Music/Music Charts/Lilypond Charts/Rock Tunes/Just The Two Of 
>> > US/Wassup MWE.ly:31:1 <0>: error: markup outside of text script or 
>> > \lyricmode
>> 
>> That happens when you are inside of some pair of braces rather than at
>> top level.
>> 
>> You probably added some spurious brace.  The input file you quote does
>> not quite correspond with the line numbers of this error message, so you
>> probably are not compiling what you think you are compiling.
> 
> You have typographical quotes in your input file:
> 
> %%% Start
> melody = \relative c' {
> \numericTimeSignature
> \time 4/4
> \clef treble
> \key f \minor
> 
> \override Staff.KeySignature.break-visibility = #all-invisible
> \override Staff.Clef.break-visibility = #all-invisible
> 
> % 1
> \bar ".|" % This had a typographical quote on the end
> 
> c'1   % This had a typographical single quote
> 
> \bar "|."
> }
> %%% End

Thanks for catching those.  Curious that they even happened since the file was 
edited solely within Frescobaldi and it does not enter typographic quotes.  
Fixing them did not fix the problem, unfortunately.

Could the problem lie in an \include .ily file instead?

Reply via email to