lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Doc: LM: Reformat ly code. (issue1056041)


From: Carl Sorensen
Subject: Re: Doc: LM: Reformat ly code. (issue1056041)
Date: Wed, 5 May 2010 18:31:21 -0600

On 5/5/10 6:11 PM, "Graham Percival" <address@hidden> wrote:

> On Wed, May 05, 2010 at 06:04:42PM -0600, Carl Sorensen wrote:
>> 
>> On 5/5/10 12:01 PM, "Graham Percival" <address@hidden> wrote:
>> 
>>> On Wed, May 5, 2010 at 11:57 AM,  <address@hidden> wrote:
>>>> I think it's an improvement.  I've made specific comments inline.
>>> 
>>> sweet mao... you're adding barline checks to every single example?!
>>> 
>>>   cis4 ees fisis, aeses |
>> 
>> For the Learning Manual, I would dispense with *all* final barline checks.
> 
> I wouldn't go that far.  Compare:
>   r8 | r4. r4 c8 | a'([ g)] f f([ e)] d | e([ d)] c bes' |
> with
>   r8 | r4. r4 c8 | a'([ g)] f f([ e)] d | e([ d)] c bes'
> 
> I'd rather have the first type; the final barline check just
> reassures you that everything matches up.

OK.  Final barline checks on examples where they add to the clarity of *that
particular* examples would be fine with me.  But when I reviewed the patch,
I felt that the final bar checks actually got in the way for me on virtually
every example.

Thanks,

Carl





reply via email to

[Prev in Thread] Current Thread [Next in Thread]