Urs: This discussion has lead me to realized an error in my thinking ( and in how Lilypond works ). My thinking was that if \override TupletNumber #'stencil = ##f stopped the number from being printed, then \override TupletNumber #'stencil = ##t would cause it to be printed.
I shall study Mr. Long's suggestion, yours, and the manual to correct my knowledge. Thank you for helping me learn and use Lilypond. Mark -----Original Message----- From: lilypond-user-bounces+carsonmark=ca.rr....@gnu.org [mailto:lilypond-user-bounces+carsonmark=ca.rr....@gnu.org] On Behalf Of u...@openlilylib.org Sent: Thursday, July 18, 2013 11:27 PM To: lilypond-user@gnu.org Subject: Re: fatal error I can't test right now, but I think the reason for your problem is the following: When you say #'stencil = ##f it's not that you hide the object but you actually _remove_ its stencil. So when you afterwards say #'stencil = ##f there isn't an object anymore LilyPond can refer to. You could however assign a new stencil with that command. Maybe Jim Long's suggestion works (don't know). If not you should either try to achieve the desired result with an other method than removing the stencil or look up how to (re-)add the appropriate stencil instead of your second example line. HTH Urs Zitat von Mark Stephen Mrotek <carsonm...@ca.rr.com>: > Mr. Kastrup: > > Thank you for your reply and suggestion. > > I check the input and found three instances of "stencil:" > > \override TupletNumber #'stencil = ##f \override TupletNumber > #'stencil = ##t \override TupletNumber #'stencil = ##f > > To me they appear to be correct. Should I be seeing something else > before or after this command? > > Thank you for your kind attention. > > Mark > > -----Original Message----- > From: lilypond-user-bounces+carsonmark=ca.rr....@gnu.org > [mailto:lilypond-user-bounces+carsonmark=ca.rr....@gnu.org] On Behalf > Of David Kastrup > Sent: Thursday, July 18, 2013 5:13 PM > To: lilypond-user@gnu.org > Subject: Re: fatal error > > Eluze <elu...@gmail.com> writes: > >> probably the file is opened somewhere else? > > Could well be the problem. At any rate, > > warning: type check for `stencil' failed; value `#t' must be of type > `stencil' > > also points to an input problem. No idea whether that will cause a > fatal error, but even if not, it is quite unlikely to do what was intended. > > -- > David Kastrup > > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
