Unless you're dealing with a great number of previously-existing files, I would put this type of information in its own file (maybe with other layout prefs) and then create two versions of that file.
I'm sure you know the trick, and it is cumbersome, but it only need be done once. Otherwise, that's the limit of my Pond'ering at this point! Neil On Fri, Sep 18, 2009 at 8:58 AM, Kieren MacMillan <[email protected]> wrote: > Hi Reinhold, > >> it might work to revert the changes that RESC does to the Staff context: >> >> \context { >> \Staff >> \consists "Axis_group_engraver" >> \remove "Hara_kiri_engraver" >> \revert Beam #'auto-knee-gap >> \revert VerticalAxisGroup #'remove-empty >> } >> >> After all, \RESC is just a shortcut for certain changes to the \Staff >> context:: >> RemoveEmptyStaffContext = \context { >> \Staff >> \remove "Axis_group_engraver" >> \consists "Hara_kiri_engraver" >> \override Beam #'auto-knee-gap = #'() >> \override VerticalAxisGroup #'remove-empty = ##t >> } > > I ended up discovering that on my own just now — but thanks for the > confirmation! > Is there any way that *doesn't* require knowing what's in \RESC, so that my > scores are "future-proofed"? > > Thanks, > Kieren. > > _______________________________________________ > lilypond-user mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/lilypond-user > -- Neil Thornock, D.M. Assistant Professor of Music Composition/Theory Brigham Young University http://neilthornock.net _______________________________________________ lilypond-user mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-user
