David, I suggest to apply patches of that kind directly to the
repository without setting up a Rietveld issue.
http://codereview.appspot.com/5437140/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypon
LGTM.
Carl
http://codereview.appspot.com/5437140/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
> There is . This
> should give you some suggestion both about other people's willingness to
> contribute and the amount of payment which is "not yet" sufficient to
> make somebody go for this project.
Thank you for the link. I wonder, that it is not in this mailinglist. (I don't
have no googlem
Hi,
thanks a lot for developing and maintaining LilyPond!
I read the way of including LilyPond files here:
http://lilypond.org/doc/v2.14/Documentation/notation/including-lilypond-files.html
especially the way where one can avoid to specify the (relative or absolute)
path of the included file:
That format is suggested from the "simple tasks" here:
http://lilypond.org/help-us.html
Dunno why right now, but that page points at 2.13 docs.
--
Phil Holmes
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/list
On Sun, Dec 04, 2011 at 11:39:03AM +0100, m...@apollinemike.com wrote:
> Le Dec 4, 2011 à 11:27 AM, Graham Percival a écrit :
>
> > This is *NOT* directed at programmers. Programmers should keep on
> > programming. This is directed at users.
>
> I think this is a great idea - I'm sure that ther
Le Dec 4, 2011 à 11:00 PM, Ralf Mattes a écrit :
> IMHO, "messy" spots attract more messy kludges - you might need you patch
> just for your next project, but once it's in there's a good chance that it'll
> stay and people will use it instead of doing it correctly.
>
I see what your saying and d
http://codereview.appspot.com/5450086/diff/3001/scm/define-grob-properties.scm
File scm/define-grob-properties.scm (right):
http://codereview.appspot.com/5450086/diff/3001/scm/define-grob-properties.scm#newcode310
scm/define-grob-properties.scm:310: stencilfied of a grob in a given
backend.")
Mi
"m...@apollinemike.com" writes:
> Le Dec 5, 2011 à 8:52 AM, d...@gnu.org a écrit :
>>
>>> IF .NOT.has-span-bar(UP)
>>> esh(UP) = min(esh(UP), 1.01)
>>> ENDIF
>>> IF .NOT.( has-span-bar(DOWN).AND.allow-span-bar )
>>> esh(DOWN)= max(esh(DOWN), -1.01)
>>> ENDIF
>>
>> No, this is just Mike's en
Le Dec 5, 2011 à 8:52 AM, d...@gnu.org a écrit :
>
> http://codereview.appspot.com/5434104/diff/1/scm/output-lib.scm
> File scm/output-lib.scm (right):
>
> http://codereview.appspot.com/5434104/diff/1/scm/output-lib.scm#newcode408
> scm/output-lib.scm:408: (define-public
> (pure-from-neighbor-in
10 matches
Mail list logo