James Harkins-2 wrote > In lilypond 2.15.36, I just hit an issue where this override caused > lilypond to exit with code 1. > > \once \override NoteColumn #'force-hshift = #1 > > Changing it to this allowed compilation to succeed: > > \once \override NoteColumn #'force-hshift = #1.0 > > I tried to make a MCE but both overrides worked in that context. > > I just wanted to ask if anyone else had seen anything like this. For the > bug squad folks and David: I do not intend this as a complete bug report; > please do not chastise me for failing to include a tiny example or > whatnot. I'm only asking for others' experiences at this point.
I'm afraid you'll have to make a more complete report because I can't reproduce any error with force-hshift = #1 tested 2.15.1 - 2.17.3 (just the ones on my pc) please also report which OS you're using! Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/Excessive-type-strictness-tp133719p133722.html Sent from the User mailing list archive at Nabble.com. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
