Updates:
Status: Verified
Comment #9 on issue 1554 by brownian.box: update midi2ly version number
http://code.google.com/p/lilypond/issues/detail?id=1554
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond@gnu
Comment #6 on issue 1554 by k-ohara5...@oco.net: update midi2ly version
number
http://code.google.com/p/lilypond/issues/detail?id=1554
As implied by comment 3, midi2ly now writes
\version "2.13.53"
in the .ly files it produces.
It would make things even more tidy, when 2.14 is out, to bump
Comment #5 on issue 1554 by colinpkc...@gmail.com: update midi2ly version
number
http://code.google.com/p/lilypond/issues/detail?id=1554
There's an implication in Jan's comment that we now have an engraver
(completion_rest_engraver) which is explicitly denied in NR 1.2.3 Automatic
note sp
Comment #4 on issue 1554 by percival.music.ca: update midi2ly version number
http://code.google.com/p/lilypond/issues/detail?id=1554
1) it causes confusion amongst users
2) if somebody is running midi2ly with version 2.12.3, then it's quite
possible that they'd use some constructs that aren't
Comment #3 on issue 1554 by jan.nieuwenhuizen: update midi2ly version number
http://code.google.com/p/lilypond/issues/detail?id=1554
I don't think we want that.
I updated the fixed version number to the earliest supported LilyPond
version a while ago, which is 2.7.38. Why require a newer versi
Updates:
Summary: update midi2ly version number
Labels: Frog
Comment #2 on issue 1554 by percival.music.ca: update midi2ly version number
http://code.google.com/p/lilypond/issues/detail?id=1554
Agreed. I think we want to keep a hard-coded value.
However, it might be nice to upd
