Hi Sebastiano and everyone,
Now that 2.24.0 is released, we need to update LSR.
Are you ready to make the update on the LSR server
if we provide updated snippets? And under what form
should the update be provided exactly?
Thanks,
Jean
OpenPGP_signature
Description: OpenPGP digital signature
I see snippets which have only updated
\version
Could somebody inverstigate this?
AFAICS the instructions here are still good:
http://lilypond.org/doc/v2.15/Documentation/contributor/lsr-to-git
and makelsr.py contains "convert -d -e", so IIRC this shouldn't
happen.
Cheers,
- Graham
__
Le 27/12/2022 à 15:06, Thomas Morley a écrit :
Well, I started to update the snippets to 2.24.0 locally.
Thank you for doing this.
Do you intend to do them all, or do you need help?
Some observations:
(1)
I'm stuck with three snippets:
a) clip-systems.ly It's tagged "doc"
I've no clue how
ves. I don't think we should use convert-ly to
> > educate our users to use the new possibilties, that's the duty of the
> > documentation.
> > And there are still cases where \remove/consists Mark_engraver is what
> > the user wants, but these messages will persis
Am Di., 27. Dez. 2022 um 15:24 Uhr schrieb Jean Abou Samra :
>
> Le 27/12/2022 à 15:06, Thomas Morley a écrit :
> > Well, I started to update the snippets to 2.24.0 locally.
>
> Thank you for doing this.
>
> Do you intend to do them all, or do you need help?
>
>
> > Some observations:
> >
> > (1)
>
very thankful if someone else could do so.
This should be a matter of running makelsr.pl and removing
all snippets from new/ present in stable/2.24, right?
Out of curiosity and not related to lsr-update, do you have an example
of 2.22.-code (where Mark_engraver is moved) which would not run in
Le 27/12/2022 à 17:06, Thomas Morley a écrit :
TODO guile message about `string-delete'
adding-fingerings-or-string-numbers-or-stroke-fingerings-outside-of-the-music-code.ly
Can be fixed by just inverting the arguments to string-delete.
Surprisingly not.
?
I took the snippet code an
Am Di., 27. Dez. 2022 um 17:11 Uhr schrieb Jean Abou Samra :
>
> Le 27/12/2022 à 17:06, Thomas Morley a écrit :
> >>>TODO guile message about `string-delete'
> >>>
> >>> adding-fingerings-or-string-numbers-or-stroke-fingerings-outside-of-the-music-code.ly
> >>
> >> Can be fixed by just inve
Le 27/12/2022 à 17:44, Thomas Morley a écrit :
Here string-delete has one argument, a procedure.
No; check the parentheses again.
OpenPGP_signature
Description: OpenPGP digital signature
ion/snippets/new and commit the new state,
> > I would be very thankful if someone else could do so.
>
>
> This should be a matter of running makelsr.pl and removing
> all snippets from new/ present in stable/2.24, right?
>
Yep, though I very often (always) struggle when I need to
Le 27/12/2022 à 18:06, Thomas Morley a écrit :
True, though it's still valid code for 2.24...
That makes a convert-ly rule even *more* important.
If code that was previously valid now results in an error, at least you
have a strong signal that you need to change something.
If it compiles f
Am Di., 27. Dez. 2022 um 17:54 Uhr schrieb Jean Abou Samra :
>
> Le 27/12/2022 à 17:44, Thomas Morley a écrit :
> > Here string-delete has one argument, a procedure.
>
>
> No; check the parentheses again.
>
I did, several times - before I got it:
My editor takes the parentheses in
((#\%
> Lateron, when LSR runs 2.24.0, we need to insert all snippets from
> /Documentation/snippets/new. This is tedious, any help would be
> great.
Sebastiano, if we send you an archive with all updated snippets: Do
you have a possibility to mass-import them into the database?
Submitting them one by
Am Di., 27. Dez. 2022 um 16:55 Uhr schrieb Thomas Morley
:
>
> Am Di., 27. Dez. 2022 um 15:24 Uhr schrieb Jean Abou Samra
> :
> >
> > Le 27/12/2022 à 15:06, Thomas Morley a écrit :
> > > (3)
> > > It's not possible to do
> > > lilypond *.ly
> > > on all snippets.
> > > Somewhere there's a bleed o
Le 31/12/2022 à 21:15, Thomas Morley a écrit :
Today I found some time :)
lilypond *.ly on all lsr-snippets fails because of the following snippets:
custom-tuning-and-midi-rendering.ly
dodecaphonic-staff.ly
dodecaphonic-staff-with-accurate-ledger-lines.ly
microtonal-notation-and-theo
ote-names on toplevel niveau.
> >
> > How to limit those settings to the current file?
>
>
> I would approach it differently: not "how to fix the snippets?", but
> "how to fix LilyPond so that these settings apply to the current file?".
>
Sure, out of my depth, though.
And any fix in lilypond would be too late for the 2.24. lsr-update.
t
>> "how to fix LilyPond so that these settings apply to the current file?".
>>
>
> Sure, out of my depth, though.
> And any fix in lilypond would be too late for the 2.24. lsr-update.
Session bleedover does not invalidate the isolated snippets but
invalidates our test
gt;>
>>>
>>> I would approach it differently: not "how to fix the snippets?", but
>>> "how to fix LilyPond so that these settings apply to the current file?".
>>>
>>
>> Sure, out of my depth, though.
>> And any fix in lily
Am Mi., 28. Dez. 2022 um 07:17 Uhr schrieb Werner LEMBERG :
>
>
> > Lateron, when LSR runs 2.24.0, we need to insert all snippets from
> > /Documentation/snippets/new. This is tedious, any help would be
> > great.
>
> Sebastiano, if we send you an archive with all updated snippets: Do
> you have a
>> Ideally, there would be a git repository to which we can actually
>> push the new files (to retain the editing history), and a script
>> that regenerates the database automatically – and vice versa.
>
> Werner, actually it's less work than expected.
> Currently /Documentations/snippets/new con
Am Mo., 2. Jan. 2023 um 13:33 Uhr schrieb Werner LEMBERG :
>
>
> >> Ideally, there would be a git repository to which we can actually
> >> push the new files (to retain the editing history), and a script
> >> that regenerates the database automatically – and vice versa.
> >
> > Werner, actually it'
>> Oh, the files in `new` are not what I'm concerned about. It's
>> rather running `convert-ly` on all other snippets in the LSR...
>
> Once LSR runs 2.24.0 Sebastiano gets a tarball with them and inserts
> the snippets.
OK, thanks. So he can actually do a mass import.
Werner
Am Mi., 28. Dez. 2022 um 07:17 Uhr schrieb Werner LEMBERG :
>
>
> > Lateron, when LSR runs 2.24.0, we need to insert all snippets from
> > /Documentation/snippets/new.
Done.
> > As final step we need to delete the ones from
> > /Documentation/snippets/new and commit the new state, I would be
> >
>> > As final step we need to delete the ones from
>> > /Documentation/snippets/new and commit the new state, I would be
>> > very thankful if someone else could do so.
>>
>> I can help with that.
>
> Did I understand correctly, you volunteered to do the final steps,
> i.e.
> (1) Delete all snippet
2011/7/8 Francisco Vila :
> 2011/7/8 Graham Percival :
>> I see snippets which have only updated
>> \version
>
> It has been very common in the past.
>
>> Could somebody inverstigate this?
>>
>> AFAICS the instructions here are still good:
>> http://lilypond.org/doc/v2.15/Documentation/contributor
2011/7/8 Graham Percival :
> I see snippets which have only updated
> \version
It has been very common in the past.
> Could somebody inverstigate this?
>
> AFAICS the instructions here are still good:
> http://lilypond.org/doc/v2.15/Documentation/contributor/lsr-to-git
> and makelsr.py contains
On Fri, Jul 08, 2011 at 11:43:18AM +0200, Francisco Vila wrote:
> 2011/7/8 Francisco Vila :
> > 2011/7/8 Graham Percival :
> >> I see snippets which have only updated
> >> \version
> >
> > It has been very common in the past.
Yes, but AFAIK I fixed that.
> > Right; it could be a bug of convert-l
On Fri, Jul 8, 2011 at 12:02 PM, Graham Percival
wrote:
> So why the \version changes in Valentin's commit?
Yeah, I did notice that; I figured it made sense because of the major
version bump. (But there probably is a better reason out there :-)
Cheers,
Valentin.
PS: I hope you're having an enjo
commit d069aeb6109be7dd0f93b1e6b65f79198335ab96
adds a single space at the end of a line to a bunch of files in LSR.
I'm not certain if that's related to the recent changes to makelsr.py,
or whether Neil automatically stripped out the extra whitespace when
committing LSR updates, or what.
Cheer
2009/11/27 Graham Percival :
> or whether Neil automatically stripped out the extra whitespace when
> committing LSR updates
I strip all the trailing whitespace with sed after downloading the LSR tarball.
Cheers,
Neil
___
lilypond-devel mailing list
On Sat, Nov 28, 2009 at 04:58:01PM +, Neil Puttock wrote:
> 2009/11/27 Graham Percival :
>
> > or whether Neil automatically stripped out the extra whitespace when
> > committing LSR updates
>
> I strip all the trailing whitespace with sed after downloading the LSR
> tarball.
Ok. Could we
2009/11/28 Graham Percival :
> Ok. Could we get this added to makelsr.py ? I'd be surprised if
> it takes more than 1 line of python to strip all trailing
> whitespace.
If I can work out how to do it in python, sure. :)
Cheers,
Neil
___
lilypond-de
At 18:07 on 28 Nov 2009, Graham Percival wrote:
> On Sat, Nov 28, 2009 at 04:58:01PM +, Neil Puttock wrote:
> > 2009/11/27 Graham Percival :
> >
> > > or whether Neil automatically stripped out the extra whitespace
> > > when committing LSR updates
> >
> > I strip all the trailing whitespace
On 14 March 2010 15:38, Valentin Villenave wrote:
> I've been trying to build the docs with the attached patches for half
> a day without succeeding, so I figure it's time I call for help :(
>
> Can someone tell me what's wrong with these commits?
I've had a quick skim through both patches, and
On 14 March 2010 21:33, Neil Puttock wrote:
> I've had a quick skim through both patches, and can't see anything
> which is obviously broken. I'm doing a test build to see what's going
> on.
My docs build has just completed without a hitch, so there doesn't
appear to be anything wrong with your
On Sun, Mar 14, 2010 at 11:38 PM, Neil Puttock wrote:
> My docs build has just completed without a hitch, so there doesn't
> appear to be anything wrong with your patches.
Thanks! I've removed trailing whitespaces, and pushed.
It's really annoying that for some weird reason I am not able to buil
On Mon, Mar 15, 2010 at 2:10 PM, Valentin Villenave
wrote:
> It's really annoying that for some weird reason I am not able to build
> either the docs, the regtests or the website.
You know what's even more annoying? When people say they can't do
something, but don't give you any info about why n
On Mon, Mar 15, 2010 at 3:44 PM, Graham Percival
wrote:
> You know what's even more annoying? When people say they can't do
> something, but don't give you any info about why not or what error
> messages they get.
I wish I had something more instructive to provide than
Renaming input to: `score
On Mon, Mar 15, 2010 at 2:54 PM, Valentin Villenave
wrote:
> I wish I had something more instructive to provide than
Umm, what command are you running here?
> Renaming input to: `score-for-diatonic-accordion.ly'
... that all looks ok...
> Compiling /home/valentin/lilypond/Documentation/out-www
On Mon, Mar 15, 2010 at 4:46 PM, Graham Percival
wrote:
> ... so obviously the error is further up in the log. Remember that
> doc error generally occur 100-1000 line before the end of the log.
> Maybe even more.
Yes, I've been browsing through the log without locating it. I'll try
harder (sigh)
On Mon, Mar 15, 2010 at 3:49 PM, Valentin Villenave
wrote:
> On Mon, Mar 15, 2010 at 4:46 PM, Graham Percival
> wrote:
>> If there's sufficient interest, we could start working on the new doc
>> build system again. But so far there seems to be zero interest in
>> that, so you'll need to learn th
Il giorno lun, 15/03/2010 alle 16.43 +, Graham Percival ha scritto:
> Issue 979 is currently blocked because a simple test case fails.
> Maybe that case has been fixed in waf's svn by now. If not, try
> asking the waf guy to fix it. I'm pretty certain he could fix it in
> 30 minutes or so, o
convert-ly currently creates commands like:
\deprecatedcrescTextCresc
this isn't a valid command, so automatic LSR updating is broken.
Could somebody fix the convert-ly rule?
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
ht
Hi Neil,
I just tried to update LSR in git, but found a whole bunch of added
whitespace above the
%% Translation
line.
I recall that we discussed this a few months ago, and you said that
you stripped out some useless whitespace with sed, and Mark Knoop
suggested a change to makelsr.py to do thi
I'm writing a "specification" for the updates for the LSR import and come up
against an issue that I don't think we've considered, so I'd like thoughts,
please.
My original assumption would the that the LSR "source" (which I believe
we've agreed will remain in $LILYPOND_GIT/Documentation/snipp
?p=lilypond.git;a=commit;h=fb65882ca80dc336938757d8d7feb5142c1eaf83
Your installed convert-ly is out of date (though not as much as the
last time you did an LSR update. ;)
Cheers,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://list
?p=lilypond.git;a=commit;h=fb65882ca80dc336938757d8d7feb5142c1eaf83
>
> Your installed convert-ly is out of date (though not as much as the
> last time you did an LSR update. ;)
Oops. Heh... I normally do out-of-tree builds, so makelsr finds the
convert-ly in my PATH.
On 18 August 2010 18:58, Graham Percival wrote:
> I just tried to update LSR in git, but found a whole bunch of added
> whitespace above the
> %% Translation
> line.
You have to run a local update after doing a full one to strip the
extra spaces (see issue 1115).
> I recall that we discussed t
"Phil Holmes" writes:
> I'm writing a "specification" for the updates for the LSR import and
> come up against an issue that I don't think we've considered, so I'd
> like thoughts, please.
>
> My original assumption would the that the LSR "source" (which I
> believe we've agreed will remain in
>
Le mardi 26 juin 2012 à 10:17 +0100, Phil Holmes a écrit :
> We have 2 options:
>
> 1) Create $LILYPOND_GIT/Documentation/snippets as a straight copy-and-paste,
> which is very simple, but proliferates directories in git, and means that an
> update should mean deleting all the subdirectories of
On Tue, Jun 26, 2012 at 11:59:14AM +0200, John Mandereau wrote:
> Le mardi 26 juin 2012 à 10:17 +0100, Phil Holmes a écrit :
> > 2) Use a script to update $LILYPOND_GIT/Documentation/snippets. This
> > deletes all the old snippets except /new; reads all the snippets in the
> > tarball; adds the
A number of files have been reverted to old syntax in the recent
commit df2ed631752793f755c92b85640341d06ece7b0c
Author: Phil Holmes
Date: Sun Jan 1 15:19:00 2012 +
Updates to LSR
Checked carefully and all OK, so pushed to staging. make, make doc OK.
Where is the point with
David Kastrup writes:
> A number of files have been reverted to old syntax in the recent
>
> commit df2ed631752793f755c92b85640341d06ece7b0c
> Author: Phil Holmes
> Date: Sun Jan 1 15:19:00 2012 +
>
> Updates to LSR
>
> Checked carefully and all OK, so pushed to staging. make,
there
shouldn't be any incorrect syntax there.
--
Phil Holmes
- Original Message -
From: "David Kastrup"
To:
Sent: Sunday, January 01, 2012 5:03 PM
Subject: What's the deal with the LSR update?
A number of files have been reverted to old syn
Original Message -
From: "David Kastrup"
To:
Sent: Sunday, January 01, 2012 5:31 PM
Subject: Re: What's the deal with the LSR update?
David Kastrup writes:
A number of files have been reverted to old syntax in the recent
commit df2ed631752793f755c92b85640341d06ece7b
"Phil Holmes" writes:
> It's a consequence of running makelsr.py on the download from the
> Lilypond Snippet Repository. AFAI understand it, makelsr runs
> convert-ly against each file and so should update the syntax where the
> update is in convert-ly.
It isn't because it merely makes the sour
- Original Message -
From: "David Kastrup"
To:
Sent: Sunday, January 01, 2012 5:31 PM
Subject: Re: What's the deal with the LSR update?
David Kastrup writes:
A number of files have been reverted to old syntax in the recent
commit df2ed631752793f755c92b85640341d0
"Phil Holmes" writes:
> Original Message -
> From: "David Kastrup"
> To:
> Sent: Sunday, January 01, 2012 5:31 PM
> Subject: Re: What's the deal with the LSR update?
>
>> And what's this?
>>
>> make
>> [...]
>>
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Sunday, January 01, 2012 6:00 PM
Subject: Re: What's the deal with the LSR update?
"Phil Holmes" writes:
Original Message -
From: "David Kastrup"
To:
Sent:
"Phil Holmes" writes:
>> git grep automatically-change-duration
>> Documentation/snippets/rhythms.snippet-list:automatically-change-durations.ly
>> dak@lola:/usr/local/tmp/lilypond$ find -name
>> automatically-change-duration.ly
>> dak@lola:/usr/local/tmp/lilypond$
>
>
> Looks like that was a sni
David Kastrup writes:
> "Phil Holmes" writes:
>
>>> git grep automatically-change-duration
>>> Documentation/snippets/rhythms.snippet-list:automatically-change-durations.ly
>>> dak@lola:/usr/local/tmp/lilypond$ find -name
>>> automatically-change-duration.ly
>>> dak@lola:/usr/local/tmp/lilypond$
On 1 January 2012 19:37, David Kastrup wrote:
> Done, so let's see if this gets through to master, and if it does, you
> might want to try the LSR updating procedure again.
You need to remove the comment block at the top, the texidoc
translations and `% begin verbatim' comments. These are all a
Neil Puttock writes:
> On 1 January 2012 19:37, David Kastrup wrote:
>
>> Done, so let's see if this gets through to master, and if it does, you
>> might want to try the LSR updating procedure again.
>
> You need to remove the comment block at the top, the texidoc
> translations and `% begin ver
David Kastrup writes:
> Neil Puttock writes:
>
>> On 1 January 2012 19:37, David Kastrup wrote:
>>
>>> Done, so let's see if this gets through to master, and if it does, you
>>> might want to try the LSR updating procedure again.
>>
>> You need to remove the comment block at the top, the texido
On Sun, Jan 01, 2012 at 06:10:00PM -, Phil Holmes wrote:
> This is a live and learn. I typically don't add untracked files to patches,
> because there are loads of them - git-cl; the aborted_edits from lily-git,
> etc., etc. I'd not realised that updates from the LSR could also add files
> an
tomatically,
or
2) make the changes manually, then put those updated files in
Documentation/snippets/new
Whichever way you choose, I would like to see a local makelsr.py
update after that, and the whole thing go through staging into
master, before anybody looks at doing a general
d the whole thing go through staging into
> master, before anybody looks at doing a general LSR update.
Option 2) is in staging (without removing the previously updated
snippets though). I am still fuzzy about where the translations are
supposed to come back from when they have been removed in snip
> > update after that, and the whole thing go through staging into
> > master, before anybody looks at doing a general LSR update.
>
> Option 2) is in staging (without removing the previously updated
> snippets though).
ok. It still needs a local makelsr.py run before we'r
If you're involved with LSR, check out the LSR update docs in the
CG on kainhofer in a day or so; please make corrections.
Could somebody process the files in input/new/revised/ ? And why
do we need this directory, anyway? Shouldn't those files just be
dumped into input/new/ ?
Cheers
Graham Percival wrote:
If you're involved with LSR, check out the LSR update docs in the
CG on kainhofer in a day or so; please make corrections.
Could somebody process the files in input/new/revised/ ? And why
do we need this directory, anyway? Shouldn't those files just be
dumped
On Thu, Jun 04, 2009 at 07:46:10PM -0500, Jonathan Kulp wrote:
> I read the diff for CG when it came in this morning and the LSR stuff
> looks good to me. If you want, we could also include the script I wrote
> for checking all the snippets at once. Carl suggested that it go in the
> docs somewh
2009/6/5 Graham Percival :
> On Thu, Jun 04, 2009 at 07:46:10PM -0500, Jonathan Kulp wrote:
>> I read the diff for CG when it came in this morning and the LSR stuff
>> looks good to me. If you want, we could also include the script I wrote
>> for checking all the snippets at once. Carl suggested th
On Fri, Jun 05, 2009 at 01:17:01PM +0100, Neil Puttock wrote:
> 2009/6/5 Graham Percival :
> > Yeah, but there are differences --
> > input/new/revised/rest-styles.ly doesn't contain tiny rests for
> > the mensural and neomensural. The version in LSR contains those
> > rests in the .ly file, but t
On Fri, Jun 5, 2009 at 6:12 AM, Graham Percival wrote:
> On Thu, Jun 04, 2009 at 07:46:10PM -0500, Jonathan Kulp wrote:
> > I read the diff for CG when it came in this morning and the LSR stuff
> > looks good to me. If you want, we could also include the script I wrote
> > for checking all the sni
On Sat, Jun 06, 2009 at 02:54:46PM -0500, Jonathan Kulp wrote:
> Graham, here's a patch with the script for running and checking
> all of the lsr snippets.
ok. IMO, osx users should set up a "lilypond" shell script, as
suggested in AU 2.something. Then you wouldn't need that special
path-to-bin
Graham Percival wrote:
On Sat, Jun 06, 2009 at 02:54:46PM -0500, Jonathan Kulp wrote:
Graham, here's a patch with the script for running and checking
all of the lsr snippets.
ok. IMO, osx users should set up a "lilypond" shell script, as
suggested in AU 2.something. Then you wouldn't need t
On Sat, Jun 06, 2009 at 06:00:23PM -0500, Jonathan Kulp wrote:
> Graham Percival wrote:
>> ok. IMO, osx users should set up a "lilypond" shell script, as
>> suggested in AU 2.something. Then you wouldn't need that special
>> path-to-binary thing. But adding this as-is certainly can't hurt
>> the
Graham Percival wrote:
On Sat, Jun 06, 2009 at 06:00:23PM -0500, Jonathan Kulp wrote:
Graham Percival wrote:
ok. IMO, osx users should set up a "lilypond" shell script, as
suggested in AU 2.something. Then you wouldn't need that special
path-to-binary thing. But adding this as-is certainly c
78 matches
Mail list logo
