You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, since I just pushed the 6.2 release, we'd be deprecating it in 6.3, but the point still stands. I would say put the question out to the user list. List all the legacy modes that we might get rid of and ask people to respond if they are still using them. If no one responds we'll mark them as deprecated.
In fact, you could probably start making the PRs that mark them as deprecated while still waiting for responses from the users. I would make a separate PR for each feature being proposed for deprecation. Then after a month or so, we can merge the ones which no one has indicated they still rely on and close those where people are still using them.
yes, I do that, because the bar-spacing algorithm change might overdo some alignment when the new alignment messes up just one symbol IMHO. For example, a low clivis with a dot in mode I antiphons of Vespers/Lauds would have the asterisk under the clivis and its dot, but I use custom macros to change maxbaroffsetleft and right to 0 and to reset it after the antiphons.
But the alignment is not strictly under the bar even in the old Solesmes books, so it's OK if it's offset a little, so long as the symbol isn't running into other characters or too far away from the bar.
Activity
rpspringuel commentedon Apr 19, 2026
Well, since I just pushed the 6.2 release, we'd be deprecating it in 6.3, but the point still stands. I would say put the question out to the user list. List all the legacy modes that we might get rid of and ask people to respond if they are still using them. If no one responds we'll mark them as deprecated.
In fact, you could probably start making the PRs that mark them as deprecated while still waiting for responses from the users. I would make a separate PR for each feature being proposed for deprecation. Then after a month or so, we can merge the ones which no one has indicated they still rely on and close those where people are still using them.
[-]Deprecations in 6.2[/-][+]Deprecations in 6.3[/+]lbssousa commentedon Apr 20, 2026
I still use old bar spacing in order to get
\GreStarand\GreDaggerproperly aligned with bars in*(:)and+(,), for example.davidweichiang commentedon Apr 20, 2026
Oh, interesting…do you switch settings just for those symbols, then?
(I believe you could get the same effect by setting maxbaroffsetleft and right to 0.)
MRoth1910 commentedon May 21, 2026
yes, I do that, because the bar-spacing algorithm change might overdo some alignment when the new alignment messes up just one symbol IMHO. For example, a low clivis with a dot in mode I antiphons of Vespers/Lauds would have the asterisk under the clivis and its dot, but I use custom macros to change maxbaroffsetleft and right to 0 and to reset it after the antiphons.
But the alignment is not strictly under the bar even in the old Solesmes books, so it's OK if it's offset a little, so long as the symbol isn't running into other characters or too far away from the bar.