OK, thanks
OK, thanks. I've seen onstarthigherlevel in the documentation after modifying \addparttocentry, and I was too lazy to improve the code :-)
OK, thanks. I've seen the onstarthigherlevel in the documentation after modifying \addparttocentry, and I was too lazy to improve the code :-)
Suggesting `tocafterskip` option for `\RedeclareSectionCommand`
This is unavoidable, I guess, since LilyPond doesn't have the ability to move grobs horizontally for such situations. BTW, this would be a very useful addition – just think of a vertically centered forte sign in piano music that makes the staves spread too much if not moved slightly to the left.
Pushed to staging as commit bb5e79204f70d8606adec4a5128979cf57ca45d4 Author: Torsten Hämmerle torsten.haemmerle@web.de Date: Thu Mar 19 01:37:16 2020 +0100 Issue 5036: 128 beaming output not producing output as expected In case of more than 4 normal-sized beams, a grid shift correction will be applied to the outside-staff quants so that the inner beams within the staff can be neatly aligned to the staff lines. If all the beams fall outside the staff (cf. stem shortening), this grid shift will ensure...
128 beaming output not producing output as expected
Please create a Rietveld issue with your patch – even if it's only a single line! If you are unsure how to do it, someone else can do this for you.