Activity for Trevor Daniels
-
Trevor Daniels posted a comment on ticket #1291
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...
-
Changed to our new Status - Shelved, meaning "Probably desirable, but impractical to implement at present due to lack of resources".
-
Support Swaralipi Musical Notation
-
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 due to lack of resources". There are many outstanding issues that would be better so categorised....
-
Test patch upload
-
James wrote: Wednesday, October 18, 2017 11:54 AM status: Started --> Invalid Patch: needs_work --> Comment: Revisiting this, the example given at the start of this issue http://lilypond.org/doc/v2.18/Documentation/notation/explicit-breaks has no corresponding entry at all in the 2.19 documentation. In fact the entire NR 4.x section is completely different. The example in the 2.18 is for overriding when LilyPond doesn't honour a manual \break or \pagebreak command by using NonMusicalPaperColumn.line-break-permission...
-
I think the best place to document this is in the snippet "Engraving ties manually", which is included in the NR at the end of http://lilypond.org/doc/v2.19/Documentation/notation/writing-rhythms#ties . In addition, two further small mods: one to correct the wording of the regtest tie-manual-vertical-tune.ly to say "If using integers or fractions, the tie will be vertically tuned for staff line avoidance. ...", and one to the LM where it discusses staff-position in section 4.6.2, to point to the...
-
I'll have a look at changing the docs to reflect this behaviour.
-
tie-configuration is partially ignored
-
Set to "needs work" while David K is investigating the feasibility of a proper solution.
-
Doc: Please document the alternativeRestores context property, including its default setting
-
Doc: Please document the alternativeRestores context property, including its default setting
-
Doc: Issue 4993 Different time signatures in alternative repeats Add warning to NR about alternatives starting with different time signatures. http://codereview.appspot.com/323450043
-
The alternativeRestores context property is documented in the IR. What I think is rather needed is a warning Note in the NR in the section dealing with alternative repeats like this: Note: If there are two or more alternatives it is assumed that they all begin with the same time signature. If this is not the case, be sure to place an appropriate time command at the start of each alternative in which the starting time signature differs from that in the first alternative. I'll prepare a patch along...
-
Bad horizontal spacing when \override LyricText #'X-offset
-
Fix a number of SCM/int confusions.
-
Fully document the short forms of the mode-changing commands
-
Pushed to Staging as 553410afdd9496f7d9f1498e755ea18de8e70596 Author: Trevor Daniels...
-
RhythmicStaff squishing chords should produce single notes
-
Pushed to Staging as c991eb5d49a1b36c81a890c4574f75d8834bb9a0 Author: Trevor Daniels...
-
Replace \set Staff.instrumentName with \with form in doc examples
-
Trevor Daniels wrote Sunday, January 22, 2017 9:18 PM Respond to Harm's comments...
-
Respond to Harm's comments http://codereview.appspot.com/313380043
-
Using \with with \chords, \drums and \figures
-
Pushed to staging as commit 27661bd698d2f501ee621beb598dd9a3b48cdbb2 Author: Trevor...
-
Doc: Issue 5034: Expand documentation of mode-changing commands Add general description...
-
RhythmicStaff squishing chords should produce single notes
-
Issue 185 Squishing chords Add a user-level interface to the event-chord-reduce function....
-
Moved comment to new Issue 5034
-
Fully document the short forms of the mode-changing commands
-
I'm not sure about enabling it by default, because it fails with parallel music....
-
It seems a shame not to finish off this issue. All it needs is a decision on the...
-
The latest patch set at Reitveld (patchset 4 https://codereview.appspot.com/313240043...
-
Doc: Issue 5032: Using \with with \chords, \drums and \figures Document the use of...
-
Using \with with \chords, \drums and \figures
-
I've amended the title and wording to more accurately reflect the issue.
-
David Kastrup wrote Sunday, January 15, 2017 12:07 PM This is interesting in as much...
-
There are several in this thread: http://lists.gnu.org/archive/html/bug-lilypond...
-
Using \chords rather than \chordmode etc renders \with ineffective.
-
Go ahead and push this right away, David.
-
Alexander Kobel wrote Friday, January 13, 2017 11:14 AM @Knut: __ should (and will)...
-
It's unclear what exactly is the problem here, but it seems to be that the spacing...
-
vertical spacing in leadsheet with text between staffs
-
Thomas Morley wrote Friday, January 06, 2017 6:50 PM Great. Thank tons. No problem...
-
Fortunately I created a backup a couple of weeks ago, so yes it can. It should be...
-
Here's a tiny example that shows the problem. The assertion failure is triggered...
-
-
Doc: CG - Add Graham to Bug Squad list
-
fingeringOrientations don't deal properly with omitted Fingering-stencils
-
Sounds like we're agreed just a doc change is required at this stage.
-
tie-configuration is partially ignored
-
Manual page breaking causing assertion failure using Windows
-
Add a a 'maximum' slope value to TupletBracket
-
Missing NR documentation for customizing the behavior of articulations in MIDI
-
Looks like this would need some digging to establish the true situation before updating...
-
Documentation - --include requires absolute paths
-
parenthesizing an accent on a cross staff note are not rendered correctly
-
Pushed to Staging as 7a6871397b80a624067ced8381fced65d4f6f246 Author: Trevor Daniels...
-
Expand description of the engraver hooks
-
Pushed to Staging as Author: Trevor Daniels t.daniels@treda.co.uk 2016-09-02 23:08:18...
-
NR: Add font list description
-
Expand description of the engraver hooks
-
Doc: Issue 4958: CG: Expand description of the engraver hooks The description of...
-
Expand description of the engraver hooks
-
Patch: Do not output CC#7 events in MIDI on dynamic changes
-
Attach lilypond source in pdf
-
This issue seems to be moribund as there has been no action for over 6 months. Reverting...
-
Automatic fret diagrams should include barre indications when fingerings are given.
-
There has been no progress on this issue for 6 months so resetting status to Acc...
-
Reverting to Status:Accepted as there has been no progress on this in over 6 mon...
-
Beams with multiple subdivisions
-
The patch provided by Valentin seems quite close to being finished, but he appears...
-
Patch: Add French-specific note names
-
-
Well, maybe this is not an intelligent way, but it works perfectly well for fixed...
-
Reverting to Status:Accepted as there is no active owner and no action for 6 mon...
-
Patch: Add an expert font tree interface
-
Reverting to Status:Accepted as there has been no progress on the patch for almost...
-
Patch: Corrects beamed cross-staff stems' pure heights
-
Patch: Approximates cross-staff slurs in VerticalAxisGroup vertical-skylines.
-
Reverting to Status:Accepted as it is almost 3 years since there was progress on...
-
dynamics, articulations etc. attached to spacers are wrongly aligned
-
Reverting to Status:Accepted as it is over a year since there was any progress on...
-
Parenthesizing multi measure rests
-
Reverting to Status:Accepted as it is over 6 months since there was substantive ...
-
Patch: Add "Editing" page/node
-
Reverting to Status:Accepted as it is over a year since there was substantive pr...
-
Patch: Web: Download: Add introductory text
-
Reverting to Status:Accepted as it is almost 2 years since there was substantive...
-
Reverting to Status:Accepted, as it is over 2 years since there was substantive ...
-
Patch: Eliminates side position calculations for system-start-text grobs.
1 >