tle bit?
>
> 3) GITSTATS
> The gitstats linked in the sponsoring pages are a great idea but they are
> out-of-date (november 2012). Any chance to keep them up-to-date
> automatically?
> Also, I'd rather link to the Authors tab:
> http://lilypond.org/~graham/gitstats-3month
http://sourceforge.net/p/testlilyissues/issues/1741/
On Fri, Oct 23, 2015 at 2:31 PM, Bernardo Barros
wrote:
> Dear all,
>
> I contributed before, maybe I will join it again, didn't know the
> situation was so bad.
>
> Something I requested many years ago was the s
Personally I find the thicker beams look much better.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Out of curiosity: guile2 will make rendering faster for lilypond?
Other advantages?
Since compilation time of big scores annoys lots of people, that would
be good to have.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mail
Phil: I can confirm your solution avoided the problem, thanks a bunch!
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Anyway, anyone has a hint about this issue?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Just found:
http://code.google.com/p/lilypond/issues/detail?id=1741&can=1&q=tablature&colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary
The correct description would be:
"Tablature Bug when pitch is higher then beh in a quarter-tone string "
__
Hi all,
What happened with the bug report about the problem with TAB using a
quarter-tone scordatura?
I remember I did spend a good time trying to isolate the problem, but
I can't find it anymore in the bug tracker.
Any news on this issue?
___
lilypond
Very nice, Reinhold!!
A suggestion: would be nice to make an option to *not* have clefs and
initial indentation.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
2011/7/1 Han-Wen Nienhuys :
> If we add patches like this for every composer's favorite avant-garde
> notation, the large parts of the lilypond codebase will shortly become
> a tangle of hard to understand dependencies; code for uncommon
> notation constructs should only be added if their implement
10 matches
Mail list logo
