> On 2 Apr 2021, at 21:46, Dmytro O. Redchuk <[email protected]> wrote: > Hi, > > as for me, this issue has been fixed in 2.22 in some way. > > https://sourceforge.net/p/testlilyissues/issues/5129/
Hi Dmytro, Matches with the new issue-tracker for lilypond: https://gitlab.com/lilypond/lilypond/-/issues/5129 Was apparently fixed with the unstable release 2.21.2 so that it landed in the 2.22 stable release. If you have any other issues on sourceforge that you're watching/following it's best to follow the corresponding gitlab issues as that's where the development team & bug squad team moved them to and nowadays track them (http://lilypond.org/bug-reports.html). regards, Hans
