2011/3/26 Damian leGassick <damianlegass...@mac.com>: > Hi all > > I've been using lilypond for years but I still can't figure out the rationale > for > > e.g. > > bar numbers - why us it: > > \override Score.BarNumber #'break-visibility blah (note capital B) > > but > > \set Score.currentBarNumber #blah (note camelCase) > > and why #(set-accidental-style etc > > and not > > \set Score.accidentalStyle or even \set Score.Accidental style > > is there any easy way to remember whether it's \set \override or #(set*?
set is for context properties and override is for element descriptions, according to http://lilypond.org/doc/v2.12/Documentation/user/lilypond/set-versus-override.html as for #(set-whatever , they are predefined one-word commands for convenience, which give values to internal variables that are not context properties or element descriptions. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
