Re: LSR is now on 2.14

[Graham Percival]

On Wed, Apr 04, 2012 at 04:29:40PM +0100, Phil Holmes wrote:
> No - that'll only tell me I've not done anything really stupid with
> makelsr. I ran it without naming a tarball, so it just updates the
> snippets with (I believe) anything in snippets/new.

That is correct.  It also updates any translations of snippets.

>  It's a sensible
> preparation for doing a more extensive update of the snippets from
> the tarball from the LSR.

Yes, sounds good.

- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Phil Holmes]

- Original Message - 
From: "James" 

To: "Phil Holmes" 
Cc: "Thomas Morley" ; "Graham Percival" 
; "lilypond-devel" 

Sent: Wednesday, April 04, 2012 4:16 PM
Subject: Re: LSR is now on 2.14



Hello,

On 4 April 2012 16:07, Phil Holmes  wrote:

- Original Message - From: "Thomas Morley"

To: "Graham Percival" 



Ok, I checked it. Only the following 37 files have to be added
manually (the others are updates of existing LSR-files)




I've updated the LSR with all the new files - i.e. I've added them to 
docs

and approved them.


We should know 2 hours from now when Patchy does it's thing and tries
to merge staging and master.

:)

James



No - that'll only tell me I've not done anything really stupid with makelsr. 
I ran it without naming a tarball, so it just updates the snippets with (I 
believe) anything in snippets/new.  It's a sensible preparation for doing a 
more extensive update of the snippets from the tarball from the LSR.


--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[James]

Hello,

On 4 April 2012 16:07, Phil Holmes  wrote:
> - Original Message - From: "Thomas Morley"
> 
> To: "Graham Percival" 
>
>
>> Ok, I checked it. Only the following 37 files have to be added
>> manually (the others are updates of existing LSR-files)
>
>
>
> I've updated the LSR with all the new files - i.e. I've added them to docs
> and approved them.

We should know 2 hours from now when Patchy does it's thing and tries
to merge staging and master.

:)

James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Phil Holmes]

- Original Message - 
From: "Thomas Morley" 

To: "Graham Percival" 


Ok, I checked it. Only the following 37 files have to be added
manually (the others are updates of existing LSR-files)



I've updated the LSR with all the new files - i.e. I've added them to docs 
and approved them.


I'm assuming the others (i.e. changed versions of existing snippets) will 
have been imported via the tarball->Seba route.


--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Phil Holmes]

- Original Message - 
From: "Thomas Morley" 

To: "Phil Holmes" 
Cc: "David Nalesnik" ; "lilypond-devel" 


Sent: Tuesday, April 03, 2012 10:33 PM
Subject: Re: LSR is now on 2.14


Am 3. April 2012 16:30 schrieb Phil Holmes :
My understanding is that, once a correct snippet is in the LSR, it should 
be

deleted from snippets/new. What will then happen is that I will grab an
updated tarball of the snippets tagged with the docs tag and run makelsr.
These will then all be imported into snippets (not snippets/new). If there
is a snippet in snippets/new it over-writes the one from the tarball.

So the next task is to check whether there are any snippets in 
snippets/new

that should not be deleted - these would be ones that only run on 2.15.x.


I'm not sure how to continue:
I just downloaded the source-tarball, lilypond-2.15.35.tar.gz and
sorted the 2.14-snippets from *Documentation/snippets/new/"
I noticed that these snippets are not completely identical to the ones
from Savannah:
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=tree;f=Documentation/snippets/new;h=cac0bba81f655a2666049823e7d21ec51bcd73cd;hb=2055f35c47a045a50a01ff4dba8524322cfc3b48

What to do?

-Harm


=

Savannah will only catch up when I've run makelsr from the tarball and 
pushed the changes to git.  I want a clear run at that, and so am planning 
to do it over the weekend.


Could you confirm that all the snippets shown in Savannah/snippets/new can 
be removed/deleted?


--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Thomas Morley]

Am 3. April 2012 16:30 schrieb Phil Holmes :
> My understanding is that, once a correct snippet is in the LSR, it should be
> deleted from snippets/new.  What will then happen is that I will grab an
> updated tarball of the snippets tagged with the docs tag and run makelsr.
> These will then all be imported into snippets (not snippets/new).  If there
> is a snippet in snippets/new it over-writes the one from the tarball.
>
> So the next task is to check whether there are any snippets in snippets/new
> that should not be deleted - these would be ones that only run on 2.15.x.

I'm not sure how to continue:
I just downloaded the source-tarball, lilypond-2.15.35.tar.gz and
sorted the 2.14-snippets from *Documentation/snippets/new/"
I noticed that these snippets are not completely identical to the ones
from Savannah:
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=tree;f=Documentation/snippets/new;h=cac0bba81f655a2666049823e7d21ec51bcd73cd;hb=2055f35c47a045a50a01ff4dba8524322cfc3b48

What to do?

-Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Thomas Morley]

Sebastiano's last mail:


Am 3. April 2012 18:31 schrieb Sebastiano Vigna :
>
> On Apr 3, 2012, at 9:21 AM, Thomas Morley wrote:
>
>> Am 3. April 2012 18:00 schrieb Sebastiano Vigna :
>>> All new snippets compiled happily. Now it shold be impossible to insert 
>>> wrong snippets (the web interface won't allow it).
>>
>> I'm happy to hear that. Am I right that now the 2.14.2-LSR-update is
>> completely successful and all other work on/with it has to be done
>> through the web-interface?
>
>
> Yes, absolutely :).
>
> Ciao,
>
>seba
>
>

:))

-Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Phil Holmes]

- Original Message - 
From: "Thomas Morley" 

To: "Phil Holmes" 
Cc: "David Nalesnik" ; "lilypond-devel" 


Sent: Tuesday, April 03, 2012 3:24 PM
Subject: Re: LSR is now on 2.14



Hi Phil,

I just checked the snippets I added to the lsr-tarball as well as our
recent lsr-addings against the snippets from
`Documentation/snippets/new/' on
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=tree;f=Documentation/snippets/new;h=cac0bba81f655a2666049823e7d21ec51bcd73cd;hb=2055f35c47a045a50a01ff4dba8524322cfc3b48

Perhaps I messed up sth or I missed recent changes. There are a few
files, now being in the LSR, which should be changed:

adjusting-lyrics-vertical-spacing.ly
comment changed position

automatic-beam-subdivisions.ly
markup-arguments were changed

changing-the-time-signature-without-affecting-the-beaming.ly
should be deleted: "This snippet is deprecated as of 2.13.5 and will
be removed in 2.14"

displaying-complex-chords.ly
should be replaced by the current version

engravers-one-by-one.ly
\consists "Tie_engraver" is doubled
(In the file on Savannah, too)


May I ask you to do this?


-Harm



My understanding is that, once a correct snippet is in the LSR, it should be 
deleted from snippets/new.  What will then happen is that I will grab an 
updated tarball of the snippets tagged with the docs tag and run makelsr. 
These will then all be imported into snippets (not snippets/new).  If there 
is a snippet in snippets/new it over-writes the one from the tarball.


So the next task is to check whether there are any snippets in snippets/new 
that should not be deleted - these would be ones that only run on 2.15.x.


--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Thomas Morley]

Hi Phil,

I just checked the snippets I added to the lsr-tarball as well as our
recent lsr-addings against the snippets from
`Documentation/snippets/new/' on
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=tree;f=Documentation/snippets/new;h=cac0bba81f655a2666049823e7d21ec51bcd73cd;hb=2055f35c47a045a50a01ff4dba8524322cfc3b48

Perhaps I messed up sth or I missed recent changes. There are a few
files, now being in the LSR, which should be changed:

adjusting-lyrics-vertical-spacing.ly
comment changed position

automatic-beam-subdivisions.ly
markup-arguments were changed

changing-the-time-signature-without-affecting-the-beaming.ly
should be deleted: "This snippet is deprecated as of 2.13.5 and will
be removed in 2.14"

displaying-complex-chords.ly
should be replaced by the current version

engravers-one-by-one.ly
\consists "Tie_engraver" is doubled
(In the file on Savannah, too)


May I ask you to do this?


-Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[David Nalesnik]

Hi Harm,

On Tue, Apr 3, 2012 at 8:45 AM, Thomas Morley  wrote:

> Hi David,
>
> I just checked our recent addings to the LSR.
>
> In unfretted-headword.ly I noticed the line:
> noflag = \once \override Flag #'style = #'no-flag
>
> could you change it to:
> noflag = \once \override Stem #'flag-style = #'no-flag
> ?
>
> Well, the noflag-Definition isn't used in the snippet, but perhaps
> someone would be puzzled about it.
>
>
Nice catch!  Fixed.

-David
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Thomas Morley]

Hi David,

I just checked our recent addings to the LSR.

In unfretted-headword.ly I noticed the line:
noflag = \once \override Flag #'style = #'no-flag

could you change it to:
noflag = \once \override Stem #'flag-style = #'no-flag
?

Well, the noflag-Definition isn't used in the snippet, but perhaps
someone would be puzzled about it.


Thanks,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Phil Holmes]

  - Original Message - 
  From: David Nalesnik 
  To: Phil Holmes 
  Cc: Thomas Morley ; lilypond-devel 
  Sent: Monday, April 02, 2012 8:29 PM
  Subject: Re: LSR is now on 2.14


  Hi,


  On Mon, Apr 2, 2012 at 11:48 AM, Phil Holmes  wrote:

Sorry about the top post.  Windows mail is sometimes a pain.  I'll do 
fretted-string-harmonics... to screech-boink.


Phil Holmes




Attached the tarball with the missing files from 
`Ducumentatione/snippets/new/'
I'll pick the following files and put them into the LSR:

alternative-breve-note.ly
changing-the-ambitus-gap.ly
changing-the-number-of-augmentation-dots-per-note.ly
changing-the-size-of-woodwind-diagrams.ly
chordchanges-for-fretboards.ly
chord-glissando-in-tablature.ly
controlling-spanner-visibility-after-a-line-break.ly
defining-an-engraver-in-scheme-ambitus-engraver.ly
dynamics-custom-text-spanner-postfix.ly
dynamics-text-spanner-postfix.ly
expressive-headword.ly
figured-bass-headword.ly
fretboards-alternate-tables.ly

Cheers,
 Harm




  I just added the remaining files.  One thing: I kept the formatting in the 
texidoc string because I noticed that this had been done in other additions.  
Should this be converted to HTML formatting?


  -David

Simple answer - don't know.  I converted @code{} to  in the 
snippets I added, since this then displays correctly in the web version of the 
LSR.  I'm assuming this gets put back to texidoc coding during the import, but 
will need to check it when I do this.

There are a few "tweaks" like this we need to remember when we document the 
process.

--
Phil Holmes
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[David Nalesnik]

Hi,

On Mon, Apr 2, 2012 at 11:48 AM, Phil Holmes  wrote:

> Sorry about the top post.  Windows mail is sometimes a pain.  I'll do
> fretted-string-harmonics... to screech-boink.
>
>
> Phil Holmes
>
>
>
> Attached the tarball with the missing files from
> `Ducumentatione/snippets/new/'
> I'll pick the following files and put them into the LSR:
>
> alternative-breve-note.ly
> changing-the-ambitus-gap.ly
> changing-the-number-of-**augmentation-dots-per-note.ly
> changing-the-size-of-woodwind-**diagrams.ly
> chordchanges-for-fretboards.ly
> chord-glissando-in-tablature.**ly 
> controlling-spanner-**visibility-after-a-line-break.**ly
> defining-an-engraver-in-**scheme-ambitus-engraver.ly
> dynamics-custom-text-spanner-**postfix.ly
> dynamics-text-spanner-postfix.**ly
> expressive-headword.ly
> figured-bass-headword.ly
> fretboards-alternate-tables.ly
>
> Cheers,
>  Harm
>
>
I just added the remaining files.  One thing: I kept the formatting in the
texidoc string because I noticed that this had been done in other
additions.  Should this be converted to HTML formatting?

-David
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Phil Holmes]

Sorry about the top post.  Windows mail is sometimes a pain.  I'll do 
fretted-string-harmonics... to screech-boink.



Phil Holmes


- Original Message - 
From: "Thomas Morley" 

To: "Phil Holmes" 
Cc: "David Nalesnik" ; "lilypond-devel" 


Sent: Monday, April 02, 2012 5:05 PM
Subject: Re: LSR is now on 2.14


Am 2. April 2012 01:36 schrieb Thomas Morley 
:

Am 1. April 2012 22:23 schrieb Phil Holmes :

From: "Thomas Morley" 

I downloaded todays LSR-tarball and removed all unnecessary headers
and versions manually.
Compiling-tests showed no problems.
I'd like to create a new tarball and send it back to Sebastiano. What
do you think?



Wow. That's a lot of work. Thanks for this. Please send it to Sebastiano.




Done.

-Harm



Sebastiano accepted the new tarball and the LSR now runs with it.
I think this work is finished.


ad 2.
I'll be happy to take a share, too. I'll prepare a tarball with the
missing files.




Attached the tarball with the missing files from 
`Ducumentatione/snippets/new/'

I'll pick the following files and put them into the LSR:

alternative-breve-note.ly
changing-the-ambitus-gap.ly
changing-the-number-of-augmentation-dots-per-note.ly
changing-the-size-of-woodwind-diagrams.ly
chordchanges-for-fretboards.ly
chord-glissando-in-tablature.ly
controlling-spanner-visibility-after-a-line-break.ly
defining-an-engraver-in-scheme-ambitus-engraver.ly
dynamics-custom-text-spanner-postfix.ly
dynamics-text-spanner-postfix.ly
expressive-headword.ly
figured-bass-headword.ly
fretboards-alternate-tables.ly

Cheers,
 Harm


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Thomas Morley]

Am 2. April 2012 01:36 schrieb Thomas Morley :
> Am 1. April 2012 22:23 schrieb Phil Holmes :
>> From: "Thomas Morley" 
>>> I downloaded todays LSR-tarball and removed all unnecessary headers
>>> and versions manually.
>>> Compiling-tests showed no problems.
>>> I'd like to create a new tarball and send it back to Sebastiano. What
>>> do you think?
>>
>>
>> Wow.  That's a lot of work.  Thanks for this.  Please send it to Sebastiano.
>>
>>
>
> Done.
>
> -Harm


Sebastiano accepted the new tarball and the LSR now runs with it.
I think this work is finished.

>>> ad 2.
>>> I'll be happy to take a share, too. I'll prepare a tarball with the
>>> missing files.
>

Attached the tarball with the missing files from `Ducumentatione/snippets/new/'
I'll pick the following files and put them into the LSR:

alternative-breve-note.ly
changing-the-ambitus-gap.ly
changing-the-number-of-augmentation-dots-per-note.ly
changing-the-size-of-woodwind-diagrams.ly
chordchanges-for-fretboards.ly
chord-glissando-in-tablature.ly
controlling-spanner-visibility-after-a-line-break.ly
defining-an-engraver-in-scheme-ambitus-engraver.ly
dynamics-custom-text-spanner-postfix.ly
dynamics-text-spanner-postfix.ly
expressive-headword.ly
figured-bass-headword.ly
fretboards-alternate-tables.ly

Cheers,
  Harm


missing.tar.gz
Description: GNU Zip compressed data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Thomas Morley]

Am 1. April 2012 22:23 schrieb Phil Holmes :
> From: "Thomas Morley" 
>> I downloaded todays LSR-tarball and removed all unnecessary headers
>> and versions manually.
>> Compiling-tests showed no problems.
>> I'd like to create a new tarball and send it back to Sebastiano. What
>> do you think?
>
>
> Wow.  That's a lot of work.  Thanks for this.  Please send it to Sebastiano.
>
>

Done.

-Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[David Nalesnik]

Hi Harm,

On Sun, Apr 1, 2012 at 3:23 PM, Phil Holmes  wrote:

> From: "Thomas Morley" 
>
>> To: "Phil Holmes" 
>> Cc: "David Nalesnik" ; "lilypond-devel" <
>> lilypond-devel@gnu.org>
>> Sent: Sunday, April 01, 2012 6:19 PM
>>
>> Subject: Re: LSR is now on 2.14
>>
>>
>> Am 1. April 2012 16:57 schrieb Phil Holmes :
>> > Thanks. Currently working on sorting out the problem with the headers -
>> > once that's done we'll set about this.
>> >
>> >
>> > Phil Holmes
>> >
>> >
>> >
>> > - Original Message -
>> > From: David Nalesnik
>> > To: Phil Holmes
>> > Cc: Thomas Morley ; lilypond-devel
>> > Sent: Sunday, April 01, 2012 3:49 PM
>> > Subject: Re: LSR is now on 2.14
>> >
>> > Hi,
>> >
>> >> Simplest way might be for Harm, David and myself to put these in the
>> >> LSR.
>> >> Don't think it'll take that long. I'd then check and approve them - so
>> >> if I
>> >> took 10 and you 2 share the others out, that should be fair? What do
>> >> you
>> >> think?
>> >
>> >
>> > Sure, I'll be happy to take a share.
>> >
>> > -David
>>
>> Hi Phil,
>>
>> my plans:
>> 1. Finish a proper LSR-update.
>> 2. Include the missing files from `Documentation/snippets/new/'
>> 3. Rewrite CG 7.7
>>
>> > ad 1.
>> I downloaded todays LSR-tarball and removed all unnecessary headers
>> and versions manually.
>> Compiling-tests showed no problems.
>> I'd like to create a new tarball and send it back to Sebastiano. What
>> do you think?
>>
>
> Wow.  That's a lot of work.  Thanks for this.  Please send it to
> Sebastiano.
>
>
>  ad 2.
>> I'll be happy to take a share, too. I'll prepare a tarball with the
>> missing files.
>>
>
> Thanks.
>
>
>  ad 3.
>> I'd like to rewrite CG 7.7 after the other work is done.
>> Removing headers and versions manually is a long lasting and boring
>> work, so your script to do it automated would be very helpful.
>>
>
> Please let me have CG words - I'll put them into the correct format.  I'll
> have the script ready in the next day or so for review.
>
>
Thank you so much for everything you've done!

-David
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Phil Holmes]

From: "Thomas Morley" 

To: "Phil Holmes" 
Cc: "David Nalesnik" ; "lilypond-devel" 


Sent: Sunday, April 01, 2012 6:19 PM
Subject: Re: LSR is now on 2.14


Am 1. April 2012 16:57 schrieb Phil Holmes :
> Thanks. Currently working on sorting out the problem with the headers -
> once that's done we'll set about this.
>
>
> Phil Holmes
>
>
>
> - Original Message -
> From: David Nalesnik
> To: Phil Holmes
> Cc: Thomas Morley ; lilypond-devel
> Sent: Sunday, April 01, 2012 3:49 PM
> Subject: Re: LSR is now on 2.14
>
> Hi,
>
>> Simplest way might be for Harm, David and myself to put these in the 
>> LSR.
>> Don't think it'll take that long. I'd then check and approve them - so 
>> if I
>> took 10 and you 2 share the others out, that should be fair? What do 
>> you

>> think?
>
>
> Sure, I'll be happy to take a share.
>
> -David

Hi Phil,

my plans:
1. Finish a proper LSR-update.
2. Include the missing files from `Documentation/snippets/new/'
3. Rewrite CG 7.7

> ad 1.
I downloaded todays LSR-tarball and removed all unnecessary headers
and versions manually.
Compiling-tests showed no problems.
I'd like to create a new tarball and send it back to Sebastiano. What
do you think?


Wow.  That's a lot of work.  Thanks for this.  Please send it to Sebastiano.


ad 2.
I'll be happy to take a share, too. I'll prepare a tarball with the
missing files.


Thanks.


ad 3.
I'd like to rewrite CG 7.7 after the other work is done.
Removing headers and versions manually is a long lasting and boring
work, so your script to do it automated would be very helpful.


Please let me have CG words - I'll put them into the correct format.  I'll 
have the script ready in the next day or so for review.


--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Thomas Morley]

Am 1. April 2012 16:57 schrieb Phil Holmes :
> Thanks.  Currently working on sorting out the problem with the headers -
> once that's done we'll set about this.
>
>
> Phil Holmes
>
>
>
> - Original Message -
> From: David Nalesnik
> To: Phil Holmes
> Cc: Thomas Morley ; lilypond-devel
> Sent: Sunday, April 01, 2012 3:49 PM
> Subject: Re: LSR is now on 2.14
>
> Hi,
>
>> Simplest way might be for Harm, David and myself to put these in the LSR.
>> Don't think it'll take that long.  I'd then check and approve them - so if I
>> took 10 and you 2 share the others out, that should be fair?  What do you
>> think?
>
>
>  Sure, I'll be happy to take a share.
>
> -David

Hi Phil,

my plans:
1. Finish a proper LSR-update.
2. Include the missing files from `Documentation/snippets/new/'
3. Rewrite CG 7.7

ad 1.
I downloaded todays LSR-tarball and removed all unnecessary headers
and versions manually.
Compiling-tests showed no problems.
I'd like to create a new tarball and send it back to Sebastiano. What
do you think?

ad 2.
I'll be happy to take a share, too. I'll prepare a tarball with the
missing files.

ad 3.
I'd like to rewrite CG 7.7 after the other work is done.
Removing headers and versions manually is a long lasting and boring
work, so your script to do it automated would be very helpful.


Best,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Phil Holmes]

Thanks.  Currently working on sorting out the problem with the headers - once 
that's done we'll set about this.


Phil Holmes


  - Original Message - 
  From: David Nalesnik 
  To: Phil Holmes 
  Cc: Thomas Morley ; lilypond-devel 
  Sent: Sunday, April 01, 2012 3:49 PM
  Subject: Re: LSR is now on 2.14


  Hi,


Simplest way might be for Harm, David and myself to put these in the LSR. 
Don't think it'll take that long.  I'd then check and approve them - so if I 
took 10 and you 2 share the others out, that should be fair?  What do you think?


   Sure, I'll be happy to take a share.


  -David___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[David Nalesnik]

Hi,

Simplest way might be for Harm, David and myself to put these in the LSR.
> Don't think it'll take that long.  I'd then check and approve them - so if
> I took 10 and you 2 share the others out, that should be fair?  What do you
> think?


 Sure, I'll be happy to take a share.

-David
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Phil Holmes]

- Original Message - 
From: "Thomas Morley" 

Subject: Re: LSR is now on 2.14


Ok, I checked it. Only the following 37 files have to be added
manually (the others are updates of existing LSR-files)

alternative-breve-note.ly
changing-the-ambitus-gap.ly
changing-the-number-of-augmentation-dots-per-note.ly
changing-the-size-of-woodwind-diagrams.ly
chordchanges-for-fretboards.ly
chord-glissando-in-tablature.ly
controlling-spanner-visibility-after-a-line-break.ly
defining-an-engraver-in-scheme-ambitus-engraver.ly
dynamics-custom-text-spanner-postfix.ly
dynamics-text-spanner-postfix.ly
expressive-headword.ly
figured-bass-headword.ly
fretboards-alternate-tables.ly
fretted-string-harmonics-in-tablature.ly
graphical-and-text-woodwind-diagrams.ly
hiding-accidentals-on-tied-notes-at-the-start-of-a-new-system.ly
keyboard-headword.ly
lyrics-old-spacing-settings.ly
making-slurs-with-complex-dash-structure.ly
non-default-tuplet-numbers.ly
numbers-as-easy-note-heads.ly
open-string-harmonics-in-tablature.ly
pitches-headword.ly
repeats-headword.ly
rhythms-headword.ly
screech-boink.ly
setting-the-double-repeat-default-for-volte.ly
simultaneous-headword.ly
slides-in-tablature.ly
snap-pizzicato-bartok-pizzicato.ly
staff-headword.ly
text-headword.ly
unfretted-headword.ly
using-the-whiteout-property.ly
vocal-headword.ly
wind-headword.ly
woodwind-diagrams-listing.ly

-Harm



Simplest way might be for Harm, David and myself to put these in the LSR. 
Don't think it'll take that long.  I'd then check and approve them - so if I 
took 10 and you 2 share the others out, that should be fair?  What do you 
think?



--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[James]

Phil,


>
> 
>
> I use LilyDev quite a bit - a slightly out of date version.  The only
> machine for which this is not true is the Ubuntu 64-bit "real" machine I use
> for build.  My PC VM is lilydev, as is my GUB VM on the big build box.
>

Oh good. I thought you only used a phys machine.


James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Phil Holmes]

- Original Message - 
From: "James" 

To: "Graham Percival" 
Cc: "lilypond-devel" 
Sent: Friday, March 30, 2012 6:57 AM
Subject: Re: LSR is now on 2.14


Hello,

On 30 March 2012 02:24, Graham Percival  wrote:
...



Well, currently I can't self-compile LilyPond or prepare a formal
patch or sth else in this direction.
Seems I have to learn a lot. ;)


Yep. To warn you: at the moment the "quick start" section of the
CG is broken; following its instructions will give you neither a
quick nor painless start.

Your options are:
1) go through the painful process of figuring out which parts are
still valid and which are not. Without a mentor, this will be
especially painful.
2) wait for lilydev to be updated (ETA: 6 weeks) and somebody to
fix up at least the short "quick start" section (ETA: 1 month
after lilydev is updated).
3) ask/wait for somebody else to handle the LSR import.

Unfortunately there is no magic wand that will let us offer you an
option other than those three. (unless I've forgotten about
something, which is possible given my mental state these days.
James: I have not forgotten about your recent work on lilydev, but
I stand behind my pessimistic estimate)


I've updated LilyDev and been working with it this week testing the
basics - it makes the code and the doc. I've given Mike a copy of the
iso (as he was the only one I knew who used LilyDev in anger) and I
FTP'd the iso to Phil's website last night. As far as I know, this is
good to go.

James



I use LilyDev quite a bit - a slightly out of date version.  The only 
machine for which this is not true is the Ubuntu 64-bit "real" machine I use 
for build.  My PC VM is lilydev, as is my GUB VM on the big build box.



--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Graham Percival]

On Fri, Mar 30, 2012 at 06:57:37AM +0100, James wrote:
> I've updated LilyDev and been working with it this week testing the
> basics - it makes the code and the doc. I've given Mike a copy of the
> iso (as he was the only one I knew who used LilyDev in anger)

actually, all official lilypond releases are built with GUB.  :)
(running as a standalone installation, not inside virtualbox)

> As far as I know, this is good to go.

If you send me a link, I'll try it out because my phd dissertation
has completely unravelled into not even being able to produce a
pluck and I could really use something simple to work on.

> but if you
> ever wanted to make the whole doc you'd need more and 1 CPU with small
> amounts of RAM would take a while to compile all the doc. For LSR you
> don't need this, obviously.

If you're just doing a normal update from LSR, then no you don't
need it.  But if somebody is going to be deleting the now-unneeded
snippets (absolutely highly recommended, and I may even make that
a Critical issue), they'll need to compile the docs to check that
they haven't typo'd something.

- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[James]

Hello,

On 30 March 2012 02:24, Graham Percival  wrote:
...

>>
>> Well, currently I can't self-compile LilyPond or prepare a formal
>> patch or sth else in this direction.
>> Seems I have to learn a lot. ;)
>
> Yep.  To warn you: at the moment the "quick start" section of the
> CG is broken; following its instructions will give you neither a
> quick nor painless start.
>
> Your options are:
> 1) go through the painful process of figuring out which parts are
> still valid and which are not.  Without a mentor, this will be
> especially painful.
> 2) wait for lilydev to be updated (ETA: 6 weeks) and somebody to
> fix up at least the short "quick start" section (ETA: 1 month
> after lilydev is updated).
> 3) ask/wait for somebody else to handle the LSR import.
>
> Unfortunately there is no magic wand that will let us offer you an
> option other than those three.  (unless I've forgotten about
> something, which is possible given my mental state these days.
> James: I have not forgotten about your recent work on lilydev, but
> I stand behind my pessimistic estimate)

I've updated LilyDev and been working with it this week testing the
basics - it makes the code and the doc. I've given Mike a copy of the
iso (as he was the only one I knew who used LilyDev in anger) and I
FTP'd the iso to Phil's website last night. As far as I know, this is
good to go.

Thomas the ISO is a 32 bit, 10.04 version of Ubuntu that can be
installed directly on hardware or, as I do, used in a Virtual Machine
on any x86 based hardware (i.e. Virtual Box for Windows/Mac/Linux).
I've compiled the binary using as little as 750mb of RAM with a single
CPU - you'll need about 10GB of disk space (give or take), but if you
ever wanted to make the whole doc you'd need more and 1 CPU with small
amounts of RAM would take a while to compile all the doc. For LSR you
don't need this, obviously.

It doesn't do GUB, but it has everything else asked for on the tracker.

I can take a look at the quick start over the weekend, but after the
iso is downloaded (and I am no programmer) I can be installed with
Virtual Box and have a compiled binary - of the latest dev version -
in less than an hour (assuming you have a relatively fast internet to
download the code) of which 80% of that is letting the computer just
run.

James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Graham Percival]

On Fri, Mar 30, 2012 at 02:03:40AM +0200, Thomas Morley wrote:
> Am 30. März 2012 01:51 schrieb Graham Percival :
> > On Fri, Mar 30, 2012 at 01:02:50AM +0200, Thomas Morley wrote:
> >> Am 30. März 2012 00:12 schrieb Sebastiano Vigna :
> >> >> _All_ "Unknown files" are from `Documentation/snippets/new' as
> >> >> requested by the Contributors Guide.
> >> >> see: 
> >> >> http://lilypond.org/doc/v2.15/Documentation/contributor/updating-lsr-to-a-new-version
> >> >
> >> > The problem is that while this is fine, there is no procedure for 
> >> > inserting *new* snippet from the .ly files. My code just look at the 
> >> > snippets in the tarballs, matches titles, and replaces the code. I mean, 
> >> > I don't even *look* at the text. So these snippets will have to be 
> >> > inserted by means of the web interface..
> >
> > That's what I expected.
> 
> I added 66 (!) files from `Documentation/snippets/new' running with 2.14.
> It will be a lot of work to add them manually using the web-interface.

Recruit somebody from -user to handle it?

Alternately, you could have a look at the java code that runs LSR
and prepare a patch which adds this capability to it.  I think
it'll be far less work just to recruit one or two people from
-user, teach them enough to do this task, then let them handle it.

> > Once you've added a snippet to LSR manually and checked that it's
> > covered by the next LSR import (I think this is only Phil at the
> > moment, but if you want to try doing an import and put the patch
> > on rietveld, that would be great), that file should be deleted
> > from Documentation/snippets/new/.
> 
> Well, currently I can't self-compile LilyPond or prepare a formal
> patch or sth else in this direction.
> Seems I have to learn a lot. ;)

Yep.  To warn you: at the moment the "quick start" section of the
CG is broken; following its instructions will give you neither a
quick nor painless start.

Your options are:
1) go through the painful process of figuring out which parts are
still valid and which are not.  Without a mentor, this will be
especially painful.
2) wait for lilydev to be updated (ETA: 6 weeks) and somebody to
fix up at least the short "quick start" section (ETA: 1 month
after lilydev is updated).
3) ask/wait for somebody else to handle the LSR import.

Unfortunately there is no magic wand that will let us offer you an
option other than those three.  (unless I've forgotten about
something, which is possible given my mental state these days.
James: I have not forgotten about your recent work on lilydev, but
I stand behind my pessimistic estimate)

- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Thomas Morley]

Am 30. März 2012 02:03 schrieb Thomas Morley :
> Am 30. März 2012 01:51 schrieb Graham Percival :
>> On Fri, Mar 30, 2012 at 01:02:50AM +0200, Thomas Morley wrote:
>>> Am 30. März 2012 00:12 schrieb Sebastiano Vigna :
>>> >> _All_ "Unknown files" are from `Documentation/snippets/new' as
>>> >> requested by the Contributors Guide.
>>> >> see: 
>>> >> http://lilypond.org/doc/v2.15/Documentation/contributor/updating-lsr-to-a-new-version
>>> >
>>> > The problem is that while this is fine, there is no procedure for 
>>> > inserting *new* snippet from the .ly files. My code just look at the 
>>> > snippets in the tarballs, matches titles, and replaces the code. I mean, 
>>> > I don't even *look* at the text. So these snippets will have to be 
>>> > inserted by means of the web interface..
>>
>> That's what I expected.
>>
>> Also note that (complete guess) only 30% of files in
>> Documentation/snippets/new can be added to LSR version 2.14.2  The
>> bulk of those files require version 2.15.0 or higher, so they must
>> be left in Documentation/snippets/new/.
>
> I added 66 (!) files from `Documentation/snippets/new' running with 2.14.
> It will be a lot of work to add them manually using the web-interface.

Ok, I checked it. Only the following 37 files have to be added
manually (the others are updates of existing LSR-files)

alternative-breve-note.ly
changing-the-ambitus-gap.ly
changing-the-number-of-augmentation-dots-per-note.ly
changing-the-size-of-woodwind-diagrams.ly
chordchanges-for-fretboards.ly
chord-glissando-in-tablature.ly
controlling-spanner-visibility-after-a-line-break.ly
defining-an-engraver-in-scheme-ambitus-engraver.ly
dynamics-custom-text-spanner-postfix.ly
dynamics-text-spanner-postfix.ly
expressive-headword.ly
figured-bass-headword.ly
fretboards-alternate-tables.ly
fretted-string-harmonics-in-tablature.ly
graphical-and-text-woodwind-diagrams.ly
hiding-accidentals-on-tied-notes-at-the-start-of-a-new-system.ly
keyboard-headword.ly
lyrics-old-spacing-settings.ly
making-slurs-with-complex-dash-structure.ly
non-default-tuplet-numbers.ly
numbers-as-easy-note-heads.ly
open-string-harmonics-in-tablature.ly
pitches-headword.ly
repeats-headword.ly
rhythms-headword.ly
screech-boink.ly
setting-the-double-repeat-default-for-volte.ly
simultaneous-headword.ly
slides-in-tablature.ly
snap-pizzicato-bartok-pizzicato.ly
staff-headword.ly
text-headword.ly
unfretted-headword.ly
using-the-whiteout-property.ly
vocal-headword.ly
wind-headword.ly
woodwind-diagrams-listing.ly

-Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Thomas Morley]

Am 30. März 2012 01:51 schrieb Graham Percival :
> On Fri, Mar 30, 2012 at 01:02:50AM +0200, Thomas Morley wrote:
>> Am 30. März 2012 00:12 schrieb Sebastiano Vigna :
>> >> _All_ "Unknown files" are from `Documentation/snippets/new' as
>> >> requested by the Contributors Guide.
>> >> see: 
>> >> http://lilypond.org/doc/v2.15/Documentation/contributor/updating-lsr-to-a-new-version
>> >
>> > The problem is that while this is fine, there is no procedure for 
>> > inserting *new* snippet from the .ly files. My code just look at the 
>> > snippets in the tarballs, matches titles, and replaces the code. I mean, I 
>> > don't even *look* at the text. So these snippets will have to be inserted 
>> > by means of the web interface..
>
> That's what I expected.
>
> Also note that (complete guess) only 30% of files in
> Documentation/snippets/new can be added to LSR version 2.14.2  The
> bulk of those files require version 2.15.0 or higher, so they must
> be left in Documentation/snippets/new/.

I added 66 (!) files from `Documentation/snippets/new' running with 2.14.
It will be a lot of work to add them manually using the web-interface.

>
> Once you've added a snippet to LSR manually and checked that it's
> covered by the next LSR import (I think this is only Phil at the
> moment, but if you want to try doing an import and put the patch
> on rietveld, that would be great), that file should be deleted
> from Documentation/snippets/new/.

Well, currently I can't self-compile LilyPond or prepare a formal
patch or sth else in this direction.
Seems I have to learn a lot. ;)

Best,
  Harm

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LSR is now on 2.14

[Graham Percival]

On Fri, Mar 30, 2012 at 01:02:50AM +0200, Thomas Morley wrote:
> Am 30. März 2012 00:12 schrieb Sebastiano Vigna :
> >> _All_ "Unknown files" are from `Documentation/snippets/new' as
> >> requested by the Contributors Guide.
> >> see: 
> >> http://lilypond.org/doc/v2.15/Documentation/contributor/updating-lsr-to-a-new-version
> >
> > The problem is that while this is fine, there is no procedure for inserting 
> > *new* snippet from the .ly files. My code just look at the snippets in the 
> > tarballs, matches titles, and replaces the code. I mean, I don't even 
> > *look* at the text. So these snippets will have to be inserted by means of 
> > the web interface..

That's what I expected.

Also note that (complete guess) only 30% of files in
Documentation/snippets/new can be added to LSR version 2.14.2  The
bulk of those files require version 2.15.0 or higher, so they must
be left in Documentation/snippets/new/.

Once you've added a snippet to LSR manually and checked that it's
covered by the next LSR import (I think this is only Phil at the
moment, but if you want to try doing an import and put the patch
on rietveld, that would be great), that file should be deleted
from Documentation/snippets/new/.

- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel