I suggest just removing the obsolete text, and skipping the additions
(unless you are worried that the manual is getting too short).
https://codereview.appspot.com/61170044/diff/20001/Documentation/notation/repeats.itely
File Documentation/notation/repeats.itely (left):
https://codereview.appsp
Here is a work-around for
https://code.google.com/p/lilypond/issues/detail?id=3834 which I suppose
suggests both a resolution and a reason not to make a distinction between
Accidental and AccidentalCautionary in the first place. (I understand there
are probably good reasons to make a distincti
2014-02-09 23:43 GMT+01:00 :
> The "more than 1 tuplet per beam group" is actually covered by the
> French beaming example.
ok. sorry for not looking carefully enough (too hasty...)
> I could include the nested tuplet stuff, but would you have any
> objection to adding it later, after this patc
On 2014/02/09 21:23:29, janek wrote:
this ROCKS!
:)
What about "more than 1 tuplet per beam group" and "nested tuplets"?
My head
explodes every time i see these examples!
The "more than 1 tuplet per beam group" is actually covered by the
French beaming example.
I could include the neste
this ROCKS!
What about "more than 1 tuplet per beam group" and "nested tuplets"? My
head explodes every time i see these examples!
best,
Janek
https://codereview.appspot.com/58610044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://li
2014-02-09 13:14 GMT+01:00 Phil Holmes :
> Documentation/snippets/creating-a-delayed-turn.ly is automatically created
> by makelsr from Documentation/snippets/new/creating-a-delayed-turn.ly.
> Therefore editing Documentation/snippets/creating-a-delayed-turn.ly will
> have no long-term effect: the e
Ah. Just needs to be deleted from snippets/New then.
--
Phil Holmes
- Original Message -
From: James
To: Phil Holmes
Cc: David Kastrup ; Jean-Charles Malahieude ; Devel ; reply
Sent: Sunday, February 09, 2014 4:17 PM
Subject: Re: NR: 1.4.1 Replaced deprecated snippet w\
Hello,
On 9 February 2014 10:16, Phil Holmes wrote:
> - Original Message - From:
> To: ;
> Cc: ;
> Sent: Sunday, February 09, 2014 9:35 AM
> Subject: Re: NR: 1.4.1 Replaced deprecated snippet w\ @lilypond
> (issue60840048)
>
>
>
> On 2014/02/08 21:55:15, dak wrote:
>>
>>> Is there a
Hello,
Taking dev off of this and moving to 'bug'
On 30 January 2014 11:21, David Kastrup wrote:
> James writes:
>
> > On 22/01/14 18:16, David Kastrup wrote:
> >> "Phil Holmes" writes:
> >>
> >>> Think it's worth putting this up as an Issue, so as not to lose it.
> >> Probably worth putting
2014-02-09 12:23 GMT+01:00 Phil Holmes :
> - Original Message - From: "Francisco Vila"
> To: "Phil Holmes"
> Cc: "Graham Percival" ; "LilyPond-Devel list"
> ;
> Sent: Sunday, February 09, 2014 10:45 AM
> Subject: Re: misplaced comment produces wrong HTML output. (issue 60880044)
>
>
>
>>
2014-02-09 11:09 GMT+01:00 :
> Can't see the diff, but I'm not too concerned about a 2-line change.
The download link does work.
https://codereview.appspot.com/download/issue59220045_1_10001.diff
The text just says what James proposed in
https://lists.gnu.org/archive/html/lilypond-devel/2014-02/
2014-02-09 11:23 GMT+01:00 Phil Holmes :
> - Original Message - From:
> To:
> Cc: ;
> Sent: Sunday, February 09, 2014 10:08 AM
> Subject: Doc: misplaced comment produces wrong HTML output. (issue 60880044)
>
>
>> Was this fix produced automatically by running import-lsr.py (or
>> whateve
- Original Message -
From:
To:
Cc: ;
Sent: Sunday, February 09, 2014 10:08 AM
Subject: Doc: misplaced comment produces wrong HTML output. (issue 60880044)
Was this fix produced automatically by running import-lsr.py (or
whatever the script is called), or was it done manually? Remem
- Original Message -
From:
To: ;
Cc: ;
Sent: Sunday, February 09, 2014 9:35 AM
Subject: Re: NR: 1.4.1 Replaced deprecated snippet w\ @lilypond
(issue60840048)
On 2014/02/08 21:55:15, dak wrote:
Is there any way in which one can actually delete this snippet file
without
getting
LGTM
https://codereview.appspot.com/54910044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Can't see the diff, but I'm not too concerned about a 2-line change.
https://codereview.appspot.com/59220045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Was this fix produced automatically by running import-lsr.py (or
whatever the script is called), or was it done manually? Remember that
this file begins with
% DO NOT EDIT this file manually
If there's a bug in the import script, then this bug will just re-appear
the next time somebody imports L
On 2014/02/08 21:55:15, dak wrote:
Is there any way in which one can actually delete this snippet file
without
getting it carried back in via LSR?
According to CG 7.4:
"Snippets used in the documentation are in
'$LILYPOND_GIT/Documentation/snippets'.
This directory contains a complete set of
18 matches
Mail list logo
