Trevor Daniels

Valentin, you wrote 25/03/2020 09:48:17 As part of my patch related to Issue 4375, I changed the error message to programming error: Multi measure rest seems misplaced. Which is at least more intelligible than getrods (): I am not spanned! (besides, that function’s no longer named get_rods). Maybe David’s suggestion would be better, though: multimeasure rest size not a multiple of bar size Or for more clarity Multi measure rest’s duration is not a multiple of the current measure length. Thoughts?...

Crash with malformed tremolo code

Change to ottavation lines

Allow left-handed fret-markups

Correct the Label to match the comments

Doc: document grob metadata in SVG output in Notation Reference

In this example of the Learning Manual we do not want to introduce all the complexity of flexible vertical spacing. I'd suggest we simply replace stretchability with minimum-distance. This \override VerticalAxisGroup.staff-staff-spacing.minimum-distance = 9 seems to work perfectly well and is quite understandable in the context of the LM.

David Kastrup wrote 11/12/2017 12:03:39 "Trevor Daniels" tdanielsmusic@users.sf.net writes: David Kastrup wrote 11/12/2017 08:48:50 We don't really have a "Wontfix" category as opposed to "Accepted" and "Invalid". That seems unfortunate since the request is definitely not invalid but it makes no sense for people on an issue fixing hunt to look here. Totally out of scope. "Wontfix" sounds a little too negative. How about "Shelved"? Meaning "Probably desirable, but impractical to implement at present...