On Thu, Nov 26, 2020 at 12:27 PM Jonas Hahnfeld <hah...@hahnjo.de> wrote:

> Am Donnerstag, dem 26.11.2020 um 11:39 -0500 schrieb Trevor Bača:
> > On Tue, Nov 24, 2020 at 6:57 PM Aaron Hill <lilyp...@hillvisions.com>
> wrote:
> >
> > > On 2020-11-24 3:44 pm, Trevor Bača wrote:
> > > > Hi,
> > > >
> > > > ### BEGIN ###
> > > >
> > > > \version "2.21.80"
> > > >
> > > > \markup { \note #"4.." #UP }
> > > >
> > > > ### END ###
> > > >
> > > > GNU LilyPond 2.21.80
> > > > Processing `test.ly'
> > > > Parsing...
> > > > test.ly:3:17: error: wrong type for argument 1.  Expecting duration,
> > > > found
> > > > "4.."
> > > > \markup { \note
> > > >                 #"4.." #UP }
> > > >
> > >
> /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/scm/lily.scm:1036:21:
> > > > In procedure reverse! in expression (ly:parse-file file-name):
> > > >
> > >
> /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/scm/lily.scm:1036:21:
> > > > Wrong type argument in position 1: (1 "4.." . #f)
> > > >
> > > > What am I missing here?
> > >
> > > The syntax changed.  You no longer specify the duration as a string,
> but
> > > as a duration:
> > >
> > > %%%%
> > > \markup { \note 4.. #UP }
> > > %%%%
> > >
> >
> > In 2.21.80?
> >
> > I'm getting something like this:
> >
> > %%%
> > \version "2.21.80"
> > \markup { \note 4.. #UP }
> > %%%
> >
> > GNU LilyPond 2.21.80
> > Processing `test.ly'
> > Parsing...
> > test.ly:2:17: error: syntax error, unexpected SYMBOL
> > \markup { \note
> >                 4.. #UP }
> > test.ly:2:26: error: Unfinished main input
> > \markup { \note 4.. #UP }
> >
> > fatal error: failed files: "test.ly"
>
> As David said, the right tool for this is convert-ly. And it will
> convert the example (if you say \version "2.20.0" at the beginning) to:
> %%%%
> \markup { \note {4..} #UP }
> %%%%
> (note the curly braces)
>


Works perfectly. Thank you!

-- 
Trevor Bača
www.trevorbaca.com
soundcloud.com/trevorbaca
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to