It works for me.
Even if I can't read Scheme I can run it, and maybe pick different
test-cases than you.
http://codereview.appspot.com/6195059/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
I like the way you showed the results of the convert-ly regexp on the
docs.
Step 1 looks good, and I hope you can find time to do the re-ordering by
hand for step 2.
http://codereview.appspot.com/6203044/diff/1018/input/regression/collision-seconds.ly
File input/regression/collision-seconds.ly
On Wed, May 9, 2012 at 5:01 PM, Janek Warchoł wrote:
> On Wed, May 9, 2012 at 8:03 AM, wrote:
>>
>> http://codereview.appspot.com/4931043/diff/1/mf/feta-noteheads.mf
>> File mf/feta-noteheads.mf (right):
>>
>> http://codereview.appspot.com/4931043/diff/1/mf/feta-noteheads.mf#newcode183
>> mf/fet
2012/5/9 damien :
> dear lilypond team.
> please can i make a suggestion for 'guitar neck diagrams.'
> a rough idea of what i mean can be found in the program called 'neckdiagrams.'
> they are similar to fretboxes. but often with landscape orientation. 3 to 12
> frets and many notes on each string.
dear lilypond team.
please can i make a suggestion for 'guitar neck diagrams.'
a rough idea of what i mean can be found in the program called 'neckdiagrams.'
they are similar to fretboxes. but often with landscape orientation. 3 to 12
frets and many notes on each string. the inclusion of Roman nume
LGTM.
Just some redundant spaces in the ArticulationEvent display method needs
removing, but then they were already there.
Cheers,
Neil
http://codereview.appspot.com/6203056/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.or
On Wed, May 9, 2012 at 8:03 AM, wrote:
>
> http://codereview.appspot.com/4931043/diff/1/mf/feta-noteheads.mf
> File mf/feta-noteheads.mf (right):
>
> http://codereview.appspot.com/4931043/diff/1/mf/feta-noteheads.mf#newcode183
> mf/feta-noteheads.mf:183: set_char_box (stemthick# * linecount + gap
Francisco Vila writes:
> 2012/5/9 David Kastrup :
>> I don't presume to understand humans: I have been diagnosed with
>> personality disorders also connected with a lack of empathy.
>
> At this point I need to express something that makes the previous
> paragraph sound better. [Just like many ot
Janek Warchoł writes:
> On Tue, May 8, 2012 at 10:21 AM, David Kastrup wrote:
>> Janek Warchoł writes:
>
>>> On Mon, May 7, 2012 at 9:54 PM, James wrote:
If this were some obscure change that 'most' LP users didn't use -
'#{ ... #}' seemed to get everyone really excited for instance,
2012/5/9 David Kastrup :
> I don't presume to understand humans: I have been diagnosed with
> personality disorders also connected with a lack of empathy.
At this point I need to express something that makes the previous
paragraph sound better. [Just like many other free software
contributors] you
"Now let's consider this calmly-" began Atticus, but Mr. Gilmer
interrupted with an objection: he was not irrelevant or immaterial,
but Atticus was browbeating the witness.
Judge Taylor laughed outright. "Oh sit down, Horace, he's doing
nothing of the sort. If anything, the wi
On Tue, May 8, 2012 at 10:21 AM, David Kastrup wrote:
> Janek Warchoł writes:
>> Meanwhile other people expressed their concerns about how it looks
>> like, the /syntax/ (user interface, not technical details).
>
> Here is when the syntax and user interface were established:
> http://lists.gnu.or
Łukasz Czerwiński wrote Sunday, April 29, 2012 12:18 PM
Thanks all three of you for your immediate reply! :) I didn't know
about the glossary. One problem with it is that for musical
terms, except for notes and rests, it works only it the opposite
direction: English -> other language, while th
James gmail.com> writes:
> The justification has so far been this
>
> 1. Some programmers like it because it does something inside the code
Not that I've heard.
The only difference in results is that users absolutely must remember
to specify the duration of the next note or lyric after s1*0,
14 matches
Mail list logo
