On Mon, 2024-01-15 at 15:24 -0800, Donald J. Stewart wrote:
> Thanks Joe, I've been looking for that gremlin, but haven't found it
> yet...
>
> Also -- I forgot to attach the denemo file!
In the file you attached when compiling the LilyPond View highlights
the first error as the text
\glissandoSkipOn = {
\override NoteColumn.glissando-skip = ##t
\hide NoteHead
\override NoteHead.no-ledgers = ##t
}
which is, indeed, wrong - there should be no backslash for a
definition:
glissandoSkipOn = {
\override NoteColumn.glissando-skip = ##t
\hide NoteHead
\override NoteHead.no-ledgers = ##t
}
The question then is, where did it come from - the directive is tagged
Allow
\glissandoSkipOn
which I'm guessing comes from custom code created with
Command: LilyPond Definition
Create a definition at the head of the LilyPond output. This can then
be referenced in the music. See LilyPond documentation.
Location: Object Menu ▶ Score
Internal Name: LilyPondDefinition
to define that variable. The mistake would then be that you tried to
define the variable starting with a backslash, which is an illegal
character in a variable name.
> > [...]
> >
> > I'm trying to get around the Lilypond' Issue 34' grace note bug by
If you have an example where "Install Grace Note Hint" fails to fix the
problem please post it to the list.
Richard
> > deleting
> > events in an orchestral score until I can get a score to print
> > cleanly.
> >
> > I've deleted all events except 1 simple note -- and I'm getting a
> > strange
> > error.
> >
> > Score->Check Score finishes with no errors, but clicking Typeset in
> > Denemo
> > Print View gives me an error...
> >
> >
> > _____________________________________________
> > D o n a l d J S t e w a r t
> > s o u n d - X
>
