Re: For those who need new features and bug fixes...

On 21 déc. 2012, at 14:01, Kieren MacMillan wrote: > Hi Mike, > >> I have two 16ish-hour flights this holiday season and I'll be filling them >> with composition, Sudoku, and LilyPond programming. So, this is the time to >> send me: >> 1) Features you need implemented. >> 2) Bugs you need f

Re: Documentation/GNUmakefile: Add dependencies for internals.texi (issue 6943053)

On 2012/12/21 07:16:08, J_lowe wrote: Johannes, I am not sure if you have push access. If not, send me a git formatted patch and I can push this for you. james Pushed author Johannes Rohrer Sun, 23 Dec 2012 10:41:16 + (10:41 +) committer James Lowe Sun, 23 Dec 2012 10:44:49 +0

Re: Documentation/GNUmakefile: Add dependencies for internals.texi (issue 6943053)

On 2012/12/23 10:49:31, J_lowe wrote: Pushed author Johannes Rohrer Sun, 23 Dec 2012 10:41:16 + (10:41 +) committer James Lowe Sun, 23 Dec 2012 10:44:49 + (10:44 +) commit579622134aba5b4c66068262f9f6ac747f0a66d7

Re: Tablature: ignore minimumStretch to/from fret zero (issue 6944061)

I think the whole issue on this "bug" is incorrect. The problem we have is that by using restrain open strings, we are telling lilypond "Don't use open strings". Then by setting minimum-fret to 0, we are saying "Do use open strings." How can we decide what behavior lilypond should have when the

Re: Tablature: ignore minimumStretch to/from fret zero (issue 6944061)

On 2012/12/23 14:24:31, Carl wrote: I think the whole issue on this "bug" is incorrect. The problem we have is that by using restrain open strings, we are telling lilypond "Don't use open strings". Then by setting minimum-fret to 0, we are saying "Do use open strings." How can we decide

Re: For those who need new features and bug fixes...

Hi Mike, > A quick note to let you know that #2 is doable via a hack. Wonderful news! > You'll have to manually put this TextSpanner in the topmost context For most of my scores, that would be fine: I use a custom "ScoreMarks" context, which is in the topmost (Score) context. > That's my not-

Re: For those who need new features and bug fixes...

On 21 December 2012 09:03, m...@mikesolomon.org wrote: > Hey all, > > I have two 16ish-hour flights this holiday season and I'll be filling them > with composition, Sudoku, and LilyPond programming. So, this is the time to > send me: > > 1) Features you need implemented. > 2) Bugs you need fixe

Re: For those who need new features and bug fixes...

On 23 December 2012 17:47, Xavier Scheuer wrote: > > What a nice proposal! Actually the known issue that "\set associatedVoice = #"lala" must be placed one syllable before the one to which the change in voice is to apply" is really really annoying. This is registered as issue #1354 I think. http

Re: Tablature: ignore minimumStretch to/from fret zero (issue 6944061)

On Sun, 23 Dec 2012 06:29:30 -0800, wrote: On 2012/12/23 14:24:31, Carl wrote: I think the whole issue on this "bug" is incorrect. The problem we have is that by using restrain open strings, we are telling lilypond "Don't use open strings". Then by setting minimum-fret to 0, we are say

Re: Uses single algorithm for side-position spacing. (issue 6827072)

The changes to side-position-interface.cc are more extensive than I am willing to figure out. Good luck. https://codereview.appspot.com/6827072/diff/38003/lily/box-quarantine.cc File lily/box-quarantine.cc (right): https://codereview.appspot.com/6827072/diff/38003/lily/box-quarantine.cc#newcod

Allows for easier creation of many Lilypond objects via Scheme. (issue 7009047)

All of this is absolutely devastatingly horrible code that is not reconcilable with sane per-session semantics and tampers with LilyPond internals in a way that has bleed-over effects into future files in the same command line. In addition, the interfaces into the exposed internals are absolutely

PATCH: Countdown to 201212

For 20:00 MST Thursday, December 27 Defect: Issue 2961 : \fret-diagram-verbose with capo > 1 puts capo in the 1st fret wrongly - R 6854106 Documentation: Issue 2741

Re: Allows for easier creation of many Lilypond objects via Scheme. (issue 7009047)

On 24 déc. 2012, at 01:10, d...@gnu.org wrote: > All of this is absolutely devastatingly horrible code that is not > reconcilable with sane per-session semantics and tampers with LilyPond > internals in a way that has bleed-over effects into future files in the > same command line. > > In additio

Re: Web: Added New Page Acknowledgements.itexi (issue 6948068)

LGTM https://codereview.appspot.com/6948068/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel