I can confirm that if I \setsecondannotation to anything other than an empty string, the problem goes away.
Henry On Friday, 13 March 2015 at 02:12:06 pm -0400, Br. Samuel Springuel wrote: > Okay, I think I've found something. I was only changing my gabc file to > reflect the MWE, not my project file. Upon doing a point by point > comparison this morning between the development runs and the installed > runs, I discovered that I had a \setsecondannotation command in my > development project file. Take that out (or make it's argument empty) > and the problem appears. Give it some non-null argument and the problem > disappears. > > Henry, can you confirm this behavior on your system? > > If this is the problem, then clearly something is happening in > \setsecondannotation that fixes the problem. Looking closely at the > output, I'd say that there are places in the code where TeX is > attempting to assign a skip to a dimension register. > \setsecondannotation would then be altering the alias so that it points > to a skip register rather than a dimension register. Assuming that's > the case, then I should be able to fix this by figuring out which > distances are getting printed on the screen and then making sure the > code attempts to assign them to a skip register before using them, not a > dimension one. > > ✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝ > Br. Samuel, OSB > (R. Padraic Springuel) > > PAX ☧ ΧΡΙΣΤΟΣ > _______________________________________________ Gregorio-users mailing list [email protected] https://mail.gna.org/listinfo/gregorio-users
