Re: LSR down?

>> The LSR looks like it's down. I don't know who is responsible for >> it so I thought I'd just post here. > > Thanks. I've written an e-mail to Sebastiano. And its online again. Werner

Re: LSR down?

> The LSR looks like it's down. I don't know who is responsible for > it so I thought I'd just post here. Thanks. I've written an e-mail to Sebastiano. Werner

Re: LSR typo: plz correct

On 20.06.24 14:41, Jean Abou Samra wrote: Done Thanks!

Re: LSR typo: plz correct

> I’m hoping to address someone with the necessary privileges to edit the > title of LSR snippet 1017: s/there/their > > https://lsr.di.unimi.it/LSR/Item?id=1017 Done signature.asc Description: This is a digitally signed message part

Re: LSR down

On Mon, Oct 30, 2023 at 3:27 AM Silvain Dupertuis < silvain-dupert...@bluewin.ch> wrote: > From my place, it works. > > https://lsr.di.unimi.it/LSR/Search?q=arpeggio > gives me 10 answers in one page > and the code for each one... > > > > Le 29.10.23 à 22:31, Knute Snortum a écrit : > > It looks l

Re: LSR down

 > Le 29 oct. 2023 à 22:33, Knute Snortum a écrit : >  > It looks like https://lsr.di.unimi.it/ is down. Does anyone know who > administers that site? Sebastiano, now in CC.

Re: LSR 1169 issue: missing point-and-click

Le mardi 20 juin 2023 à 11:43 +0200, Simon Albrecht a écrit : > Hello everyone, > > it’s great to have LSR 1169 and it seems to be working as it should—many > thanks to Jean Abou Samra and Werner Lemberg! > > However I’m sorry to write this mail because there is one issue I found > ;) Any sylla

Re: LSR 1122 "Naturalize music"

Am So., 7. März 2021 um 13:11 Uhr schrieb Thomas Morley : > > Hi all, > > I cross-post this to user- and devel-list: > > The unapproved LSR-snippet: > https://lsr.di.unimi.it/LSR/Item?u=1&id=1122 > basically duplicates the doc-tagged: > https://lsr.di.unimi.it/LSR/Snippet?id=266 > > If nobody speak

Re: LSR 1118 "Double bar line as system start" currently unapproved

Am Mo., 28. Dez. 2020 um 17:42 Uhr schrieb Jean Abou Samra : > > To the author of said snippet > lsr.di.unimi.it/LSR/Item?u=1&id=1118 > > Thanks for your snippet. > > Though, wouldn't it be much more elegant (and shorter) to get rid of > the stencil-override by setting `systemStartDelimiter` and si

Re: LSR 1119 Force clef change in alternatives

Am Mo., 2. Nov. 2020 um 11:32 Uhr schrieb Pierre Perol-Schneider : > > Done! Thanks for the reminder Harm. > Cheers > Pierre > > Le ven. 30 oct. 2020 à 22:19, Thomas Morley a > écrit : >> >> To the author (Pierre?) of >> lsr.di.unimi.it/LSR/Item?u=1&id=1119 >> >> Many thanks for your snippet, tho

Re: LSR 1119 Force clef change in alternatives

Ok Aaron. Cheers, Pierre Le ven. 30 oct. 2020 à 23:45, Aaron Hill a écrit : > On 2020-10-30 2:19 pm, Thomas Morley wrote: > > To the author (Pierre?) of > > lsr.di.unimi.it/LSR/Item?u=1&id=1119 > > > > Many thanks for your snippet, though, please add a description to it. > > ;) > > Would this w

Re: LSR 1119 Force clef change in alternatives

Done! Thanks for the reminder Harm. Cheers Pierre Le ven. 30 oct. 2020 à 22:19, Thomas Morley a écrit : > To the author (Pierre?) of > lsr.di.unimi.it/LSR/Item?u=1&id=1119 > > Many thanks for your snippet, though, please add a description to it. ;) > > Thanks, > Harm > >

Re: LSR 1119 Force clef change in alternatives

Am Fr., 30. Okt. 2020 um 23:45 Uhr schrieb Aaron Hill : > > On 2020-10-30 2:19 pm, Thomas Morley wrote: > > To the author (Pierre?) of > > lsr.di.unimi.it/LSR/Item?u=1&id=1119 > > > > Many thanks for your snippet, though, please add a description to it. > > ;) > > Would this work better to avoid th

Re: LSR 1119 Force clef change in alternatives

On 2020-10-30 2:19 pm, Thomas Morley wrote: To the author (Pierre?) of lsr.di.unimi.it/LSR/Item?u=1&id=1119 Many thanks for your snippet, though, please add a description to it. ;) Would this work better to avoid the hidden note showing up in MIDI? \grace s4 \once \override Staff.Cl

Re: LSR contribution

Am Mo., 10. Feb. 2020 um 22:15 Uhr schrieb Michael Käppler : > > Am 10.02.2020 um 20:51 schrieb Thomas Morley: > > Am Mo., 10. Feb. 2020 um 10:11 Uhr schrieb Michael Käppler > > : > >> > >> Hi Harm, > >> > >>> Fine with me, I already updated the LSR-code, for now unapproved. > >>> Please have a lo

Re: LSR contribution

Am 10.02.2020 um 20:51 schrieb Thomas Morley: Am Mo., 10. Feb. 2020 um 10:11 Uhr schrieb Michael Käppler : Hi Harm, Fine with me, I already updated the LSR-code, for now unapproved. Please have a look whether all is ok, snippet-description and the like. Everything ok now, please approve if y

Re: LSR contribution

Am Mo., 10. Feb. 2020 um 20:43 Uhr schrieb Michael Käppler : > > Am 10.02.2020 um 10:10 schrieb Michael Käppler: > > > > > > Do you have any idea how to preserve indentation within blocks? > > Inserting   or the like seems hacky, inline-css-styling too... > Ok, found out that the combination of a

Re: LSR contribution

Am Mo., 10. Feb. 2020 um 10:11 Uhr schrieb Michael Käppler : > > > Hi Harm, > > > Fine with me, I already updated the LSR-code, for now unapproved. > > Please have a look whether all is ok, snippet-description and the like. > Thank you for updating! > Will update the description this evening. > Do

Re: LSR contribution

Am 10.02.2020 um 10:10 schrieb Michael Käppler: Do you have any idea how to preserve indentation within blocks? Inserting   or the like seems hacky, inline-css-styling too... Ok, found out that the combination of and tags does work well for that purpose. Probably one suggestion: How abou

Re: LSR contribution

Hi Harm, Fine with me, I already updated the LSR-code, for now unapproved. Please have a look whether all is ok, snippet-description and the like. Thank you for updating! Will update the description this evening. Do you have any idea how to preserve indentation within blocks? Inserting   or

Re: LSR contribution

Hi Michael, Am Mi., 5. Feb. 2020 um 14:54 Uhr schrieb Michael Käppler : > > Hi Harm, > sorry that I did not respond for over one month... Many other things had > to be done. Same here... > Now I would like to finish this snippet to be free for new interesting > things. ;) > > I did substantially

Re: LSR contribution

Hi Harm, sorry that I did not respond for over one month... Many other things had to be done. Now I would like to finish this snippet to be free for new interesting things. ;) I did substantially rework some parts of the engraver, namely switching to a list-processing-way of dealing with current/

Re: LSR 782 Time signature with alternate in parantheses

Am Fr., 10. Jan. 2020 um 07:59 Uhr schrieb Dave Higgins : > > I discovered in using the time signature with alternate in parantheses > that if a 2-digit number is used, the column is not centered. > > Adding center to the column directive resolves this. > > #(define ((time-parenthesized-time up dow

Re: LSR contribution

Am So., 29. Dez. 2019 um 12:11 Uhr schrieb Thomas Morley : > Some other remarks: [...] And a general one. If a note is last in previous interval and first in a new one, then the color from the new one is done, leaving the first of the previous interval with the for it set color: \score { <<

Re: LSR contribution

Hi Michael, Am Fr., 27. Dez. 2019 um 16:12 Uhr schrieb Michael Käppler : > > Hi Harm, > thanks for your comments and this inspiring discussion! me too! > I would like to discuss a couple of things further. > My current version is attached. > > Along with it, I added a basic check for the user p

Re: LSR contribution

Hi Harm, thanks for your comments and this inspiring discussion! I would like to discuss a couple of things further. My current version is attached. You try to give the user always meaningful warning-messages. That's great, putting out really helpful messages is hard work... Alas, speaking only

Re: LSR contribution

Am Sa., 21. Dez. 2019 um 00:35 Uhr schrieb Michael Käppler : > > Hi Harm et al., > attached is my updated version. > I decided to split up the validity checks from the actual engraver, > because otherwise in case of invalid parameters the engraver would > only be instantiated to do nothing and neve

Re: LSR contribution

Btw. what I do not understand is why (process-acknowledged) is called multiple times after one grob has been acknowledged, it is even called >before< any grob has been acknowledged. You can notice this clearly in input/regression/scheme-engraver.ly Cheers, Michael Am 16.12.2019 um 01:50 schrieb

Re: LSR contribution

Hi Harm et al., attached is my updated version. I decided to split up the validity checks from the actual engraver, because otherwise in case of invalid parameters the engraver would only be instantiated to do nothing and nevertheless have its acknowledger called every time. The code is much more

Re: LSR contribution

Hi Harm, many thanks for your comments and for the time you spent with doing work that I should have been done. I already thought about adjusting the engraver to take several intervals into account, but left it for simplicity (of the engraver, not of the examples ;)) But you are absolutely right t

Re: LSR contribution

Am So., 15. Dez. 2019 um 21:47 Uhr schrieb Thomas Morley : > > Am So., 15. Dez. 2019 um 21:17 Uhr schrieb Michael Käppler > : > > > > Hi all, > > a few days ago I submitted a snippet to the LSR (title "Coloring > > successive intervals"). I can see it in the snippet database, > > but not in the we

Re: LSR contribution

Am So., 15. Dez. 2019 um 21:17 Uhr schrieb Michael Käppler : > > Hi all, > a few days ago I submitted a snippet to the LSR (title "Coloring > successive intervals"). I can see it in the snippet database, > but not in the webpage. The "Contributing" section of LSR states, that: > > "Once the snippet

Re: LSR contribution

Hi Michael, Here it is: http://lsr.di.unimi.it/LSR/Item?id=1100 Cheers, Pierre Le dim. 15 déc. 2019 à 21:18, Michael Käppler a écrit : > Hi all, > a few days ago I submitted a snippet to the LSR (title "Coloring > successive intervals"). I can see it in the snippet database, > but not in the web

Re: LSR management

Folks, I've just tried http://lsr.di.unimi.it/LSR/Search and it works fine. > It may not be a good thing that nobody seems to know who runs and > manages LSR. Uh, oh, it was and still is Sebastiano Vigna. This has never changed. Seems there is a lot FUD around here... > Should we devote

Re: LSR management

Could LSR be functionally mirrored as a GitHub repo? On Sat, Nov 16, 2019, 5:17 PM Andrew Bernard wrote: > It may not be a good thing that nobody seems to know who runs and > manages LSR. Should we devote any time to making this a more robust > situation. given how much people refer to it, and w

Re: LSR-snippet 1071 "Percussion example" incomplete

Am Do., 3. Okt. 2019 um 11:43 Uhr schrieb Thomas Morley : > > To the author of LSR-snippet 1071 "Percussion example", > > this snippet > lsr.di.unimi.it/LSR/Item?u=1&id=1071 > is obviously not complete (probably a copy/paste-error), please add > the missing parts. > > Otherwise I'll delete it soon.

Re: LSR clef change at beginning of the piece

On 07.09.2018 03:17, Simon Albrecht wrote: Hello everybody, here’s two suggestions for the LSR snippets dealing with an initial clef change before the first note of a piece: #956 works with a hidden grace note; this creates an unsightly gap that can b

Re: LSR clef change at beginning of the piece

On 07.09.2018 03:17, Simon Albrecht wrote: Hello everybody, here’s two suggestions for the LSR snippets dealing with an initial clef change before the first note of a piece: #956 works with a hidden grace note; this creates an unsightly gap that can b

Re: LSR search

On 6/8/2018 9:56 PM, Andrew Bernard wrote: What has happened to the LSR search engine? It has different ordering options, with the hard to understand 'late' and 'early' order, and choosing those it fails to return any results. Has this code been changed recently? Where is the best place to p

Re: LSR search

2018-06-09 3:56 GMT+02:00 Andrew Bernard : > What has happened to the LSR search engine? It has different ordering > options, with the hard to understand 'late' and 'early' order, and choosing > those it fails to return any results. > > Has this code been changed recently? > > Where is the best pla

Re: LSR search engine improvements

On Fri, Apr 28, 2017 at 5:03 AM, Andrew Bernard wrote: > Hi All, > > I have been working with the maintainer of the Lilypond Snippet Repository > to make a minor but very useful improvement to the custom search engine for > LSR. > Many thanks, Andrew! Ralph -- Ralph Palmer Brattleboro, VT USA

Re: LSR down

2017-04-24 5:52 GMT+02:00 Andrew Bernard : > LSR down again. > > Who is the maintainer? I'd be happy to mail them. > > Andrew :(( I'll send you the contact-data privately, afaik he's not subscribed to the user-list. Cheers, Harm ___ lilypond-user m

Re: LSR down?

Down in Oregon. --- Knute Snortum (via Gmail) On Wed, Mar 29, 2017 at 1:42 PM, Juan Cristóbal Cerrillo < jccerri...@gmail.com> wrote: > Hello, > > Also down in Mexico. > > best, > jc > > On Mar 29, 2017, at 11:10 AM, Xavier Scheuer wrote: > > Hello everybody, > > It is down here (ERR_CONNECTIO

Re: LSR down?

Hello, Also down in Mexico. best, jc > On Mar 29, 2017, at 11:10 AM, Xavier Scheuer wrote: > > Hello everybody, > > It is down here (ERR_CONNECTION_TIMED_OUT). > Is it just me (Belgium here), or it is down again? > > This raises (again) the question of LSR mirroring, that I asked > some year

Re: LSR down?

Hello everybody, It is down here (ERR_CONNECTION_TIMED_OUT). Is it just me (Belgium here), or it is down again? This raises (again) the question of LSR mirroring, that I asked some years ago. Do we have some nice people from lilypond-user who have a server and could set up a LSR mirror, so users

Re: LSR down?

Hi Harm, Snippets seems to be able to swim all the way over to Australia again now. Andrew On 28 March 2017 at 07:25, Thomas Morley wrote: > > May I ask for feedback whether it works out there as well? > > ___ lilypond-user mailing list lilypond-use

Re: LSR down?

On Mon, Mar 27, 2017 at 3:21 PM, caagr98 [via Lilypond] < ml-node+s1069038n201626...@n5.nabble.com> wrote: > Works for me. The snippet took a little longer to load than usual, but > that was probably just my internet. > Works for me, too! - Abraham -- View this message in context: http://li

Re: LSR down?

Works for me. The snippet took a little longer to load than usual, but that was probably just my internet. Any idea what made it break (other than just "daylight saving time")? On 03/27/17 22:25, Thomas Morley wrote: 2017-03-27 9:24 GMT+02:00 Malte Meyn : Am 27.03.2017 um 02:30 schrieb Andr

Re: LSR down?

2017-03-27 9:24 GMT+02:00 Malte Meyn : > > > Am 27.03.2017 um 02:30 schrieb Andrew Bernard: >> LSR still down as at 0030 UTC here in Australia. >> >> Andrew > > No time zone problems here so http://lsr.di.unimi.it/LSR/Snippet?id=1007 > shows up correctly but the search gives no results: > http://ls

Re: LSR down?

Am 27.03.2017 um 02:30 schrieb Andrew Bernard: > LSR still down as at 0030 UTC here in Australia. > > Andrew No time zone problems here so http://lsr.di.unimi.it/LSR/Snippet?id=1007 shows up correctly but the search gives no results: http://lsr.di.unimi.it/LSR/Search?q=notehead ___

RE: LSR down?

LSR still down as at 0030 UTC here in Australia. Andrew ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: LSR down?

2017-03-26 11:15 GMT+02:00 Thomas Morley : > 2017-03-26 8:51 GMT+02:00 : >> It's down for me. http://lsr.di.unimi.it/LSR/Snippet?id=1007 says something >> about timezones (CEST in unrecognized). While the search page works, the >> results are empty. > > I informed the LSR admin about it. > > Cheer

Re: LSR down?

2017-03-26 8:51 GMT+02:00 : > It's down for me. http://lsr.di.unimi.it/LSR/Snippet?id=1007 says something > about timezones (CEST in unrecognized). While the search page works, the > results are empty. I informed the LSR admin about it. Cheers, Harm ___

Re: LSR down?

Another reason to repeal daylight saving time in the EU :D Am 26.03.2017 um 08:51 schrieb caag...@gmail.com: > It's down for me. http://lsr.di.unimi.it/LSR/Snippet?id=1007 says > something about timezones (CEST in unrecognized). While the search page > works, the results are empty. > > On 03/26/1

Re: LSR down?

It's down for me. http://lsr.di.unimi.it/LSR/Snippet?id=1007 says something about timezones (CEST in unrecognized). While the search page works, the results are empty. On 03/26/17 08:48, Malte Meyn wrote: Am 26.03.2017 um 07:21 schrieb Andrew Bernard: Is LSR down for others? Not for me: h

Re: LSR down?

Am 26.03.2017 um 07:21 schrieb Andrew Bernard: > Is LSR down for others? Not for me: http://lsr.di.unimi.it/LSR/Search (Probably you know already that dsi.unimi.it changed to di.unimi.it some years ago; but there are old links pointing to the old domain in mail archives etc.) __

Re: LSR search interface: syntax errors

Hi Simon, I don't think you can. I have tried this type of search in the past. I think the search engine is written by the chap who hosts LSR. Maybe we have to write to him. A read of the search engine manual revealed nothing of any use. Apparently it cannot deal with punctuation characters, alth

Re: lSR=197

g' a' b' r4}  \layout {}}  % From: MING TSANG To: "lilypond-user@gnu.org" ; Simon Albrecht Sent: Saturday, December 17, 2016 6:45 PM Subject: Re: lSR=197 David,Thank you for showing that LSR-197 compiles fine with utf-8 characters on Debian.  I think under

Re: lSR=197

-usermailinglist Sent: Saturday, December 17, 2016 5:10 PM Subject: Re: lSR=197 On Sat 17 Dec 2016 at 18:38:59 (+0100), Simon Albrecht wrote: > On 17.12.2016 17:41, MING TSANG wrote: > >Window 10 has no problem use UTF-8  .ly file. after compile > >through Frecobaldi .pdf and .mid fi

Re: lSR=197

On Sat 17 Dec 2016 at 18:38:59 (+0100), Simon Albrecht wrote: > On 17.12.2016 17:41, MING TSANG wrote: > >Window 10 has no problem use UTF-8 .ly file. after compile > >through Frecobaldi .pdf and .mid files are created. > >It seems that internal working of lilypond and its associated > >programs n

Re: lSR=197

On Sat 17 Dec 2016 at 16:31:33 (+), MING TSANG wrote: > sorry I hit the wrong key before I complete the email.Here is the other email > message intended to send.I attached a small snippet contains UTF-8 in file > name if compile fine with pdf file name contains the UTF-8.However the log > fi

Re: lSR=197

On 17.12.2016 17:41, MING TSANG wrote: Window 10 has no problem use UTF-8 .ly file. after compile through Frecobaldi .pdf and .mid files are created. It seems that internal working of lilypond and its associated programs not handling it. I was wondering there is a work-around? Well, you were

Re: lSR=197

. From: Simon Albrecht To: MING TSANG ; Lilypond-usermailinglist Sent: Saturday, December 17, 2016 11:07 AM Subject: Re: lSR=197 On 17.12.2016 17:02, MING TSANG wrote: > UTF-8 as file name It does not come as a surprise that non-ASCII file names cause trouble on windows. Simply do

Re: lSR=197

: Saturday, December 17, 2016 4:31 PM Subject: Re: lSR=197 sorry I hit the wrong key before I complete the email. Here is the other email message intended to send. I attached a small snippet contains UTF-8 in file name if compile fine with pdf file name contains the UTF-8. However the log file

Re: lSR=197

sorry I hit the wrong key before I complete the email.Here is the other email message intended to send.I attached a small snippet contains UTF-8 in file name if compile fine with pdf file name contains the UTF-8.However the log file cannot display UTF-8 file name (see red text below).Starting l

Re: lSR=197

On 17.12.2016 17:02, MING TSANG wrote: UTF-8 as file name It does not come as a surprise that non-ASCII file names cause trouble on windows. Simply don’t do that. Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.o

Re: LSR 357: "Dynamics context is now included by default"

2016-12-09 4:56 GMT+01:00 Joel C. Salomon : > I’ve been using a variant of the LSR 357 “centered dynamics” template > from , but I notice that the > documentation says: > >> This snippet demonstrates how this was achieved with older versions >> of LilyPond; t

Re: LSR - file information [0.24759]

2016-11-28 2:26 GMT+01:00 Andrew Bernard : > Hi Harm, > > > In your code, isn't it just slightly odd breaking scheme for a function > across several calls to #define in lilypond? While that seems to be possible > (although strangely I can't get your code to compile, with unhelpful error > messages,

Re: LSR - file information [0.24759]

2016-11-28 0:51 GMT+01:00 David Wright : > On Sun 27 Nov 2016 at 22:51:15 (+0100), Thomas Morley wrote: >> 2016-11-27 19:48 GMT+01:00 Trevor Daniels : >> > >> > David Kastrup wrote Sunday, November 27, 2016 5:14 PM >> > >> >> File names are a tricky area in itself. I think that there is some >> >>

Re: LSR - file information [0.24759]

Hi Harm, In your code, isn't it just slightly odd breaking scheme for a function across several calls to #define in lilypond? While that seems to be possible (although strangely I can't get your code to compile, with unhelpful error messages, but never mind that), would one not write a single fun

Re: LSR - file information [0.24759]

On Sun 27 Nov 2016 at 22:51:15 (+0100), Thomas Morley wrote: > 2016-11-27 19:48 GMT+01:00 Trevor Daniels : > > > > David Kastrup wrote Sunday, November 27, 2016 5:14 PM > > > >> File names are a tricky area in itself. I think that there is some > >> normalization process involved in some systems t

Re: LSR - file information [0.24759]

2016-11-27 19:48 GMT+01:00 Trevor Daniels : > > David Kastrup wrote Sunday, November 27, 2016 5:14 PM > >> File names are a tricky area in itself. I think that there is some >> normalization process involved in some systems that tries to make sure >> that something like an ä will be recognized reg

Re: LSR - file information [0.24759]

David Kastrup wrote Sunday, November 27, 2016 5:14 PM > File names are a tricky area in itself. I think that there is some > normalization process involved in some systems that tries to make sure > that something like an ä will be recognized regardless of whether it is > written as a single cha

Re: LSR - file information [0.24759]

2016-11-27 18:14 GMT+01:00 David Kastrup : > Thomas Morley writes: > >> I tracked it down to a guile problem. >> >> I stored in a file called filename_名字.scm nothing else then: >> >> ; >> >> (newline) >> (write (command-line)) >> >> (newline) >> (write (map string->symbol (

Re: LSR - file information [0.24759]

Thomas Morley writes: > I tracked it down to a guile problem. > > I stored in a file called filename_名字.scm nothing else then: > > ; > > (newline) > (write (command-line)) > > (newline) > (write (map string->symbol (command-line))) > > ; > > Navigat

Re: LSR - file information [0.24759]

Sent: Saturday, November 26, 2016 11:49 PM Subject: Re: LSR - file information [0.24759] Hi Ming, Indeed yes that fails, using a filename with Chinese characters. As as aside, I myself have been learning to read and write and speak Chinese for a long time. However, I have never had the need

Re: LSR - file information [0.24759]

2016-11-27 5:49 GMT+01:00 Andrew Bernard : > Hi Ming, > > > Indeed yes that fails, using a filename with Chinese characters. As as > aside, I myself have been learning to read and write and speak Chinese for a > long time. However, I have never had the need to do it in Lilypond. I am not > sure tha

Re: LSR - file information [0.24759]

Hi Ming, Indeed yes that fails, using a filename with Chinese characters. As as aside, I myself have been learning to read and write and speak Chinese for a long time. However, I have never had the need to do it in Lilypond. I am not sure that lilypond has focused on Chinese character support ver

Re: LSR - file information [0.24759]

OIR_2016/filename_.ly"Unbound variable: modtNo such file or directory: "rive/CHOIR_2016/filename_.ly"No such file or directory: "rive/CHOIR_2016/filename_.ly"fatal error: failed files: "C:/Users/user/Google Drive/CHOIR_2016/filename_.ly"Exited with ret

Re: LSR - file information [0.24759]

/CHOIR_2016/filename.ly"Unbound variable: modtNo such file or directory: "rive/CHOIR_2016/filename.ly"No such file or directory: "rive/CHOIR_2016/filename.ly"fatal error: failed files: "C:/Users/user/Google Drive/CHOIR_2016/filename.ly"Exited with return code 1.

Re: LSR - file information [0.24759]

Hello Ming, LSR 197 works fine at 2.19.51 with no conversion. It's really just mostly Scheme, not lilypond, and the syntax for Scheme has not changed. Compiles for me without error. Try running with a conversion. I cannot see the error in your appended output. Where is it? Andrew _

Re: Q re LSR snippet 744

2016-03-19 21:51 GMT+01:00 Thomas Morley : > 2016-03-19 21:43 GMT+01:00 Michael Gerdau : >>> Because it's an really old snippet, I rewrote large parts of it, >>> reflecting functionality being in the source meanwhile. >>> Please test, if no glitch escaped me, I'll replace the old code with >>> the

Re: Q re LSR snippet 744

2016-03-19 21:43 GMT+01:00 Michael Gerdau : >> Because it's an really old snippet, I rewrote large parts of it, >> reflecting functionality being in the source meanwhile. >> Please test, if no glitch escaped me, I'll replace the old code with >> the one below: > > All my own use cases behave visual

Re: Q re LSR snippet 744

> Because it's an really old snippet, I rewrote large parts of it, > reflecting functionality being in the source meanwhile. > Please test, if no glitch escaped me, I'll replace the old code with > the one below: All my own use cases behave visually unchanged with the rewritten version. Best wish

Re: Q re LSR snippet 744

On 19.03.2016 15:30, Thomas Morley wrote: 2016-03-19 12:41 GMT+01:00 Michael Gerdau : somewhere between 2.14. and 2.16. LilyPond internals changed how the Hyphen is represented. The check for (eq? (ly:music-property lyrics 'name) 'HyphenEvent) in (lyrics->list lyrics) will never be true nowaday

Re: Q re LSR snippet 744

2016-03-19 12:41 GMT+01:00 Michael Gerdau : >> somewhere between 2.14. and 2.16. LilyPond internals changed how the >> Hyphen is represented. >> >> The check for >> (eq? (ly:music-property lyrics 'name) 'HyphenEvent) >> in >> (lyrics->list lyrics) >> will never be true nowadays. > > Ah...ok...it's

Re: Q re LSR snippet 744

Thomas Morley writes: > 2016-03-19 11:02 GMT+01:00 Michael Gerdau : >> Hi list, >> >> I'm playing with LSR snippet 744 and wish to make a small amendment to >> its functionality. While trying to understand what it does I think it >> is not working as it should. >> >> Here is the link: http://lsr.

Re: Q re LSR snippet 744

> somewhere between 2.14. and 2.16. LilyPond internals changed how the > Hyphen is represented. > > The check for > (eq? (ly:music-property lyrics 'name) 'HyphenEvent) > in > (lyrics->list lyrics) > will never be true nowadays. Ah...ok...it's not me being too stupid to understand the logic then :

Re: Q re LSR snippet 744

2016-03-19 11:02 GMT+01:00 Michael Gerdau : > Hi list, > > I'm playing with LSR snippet 744 and wish to make a small amendment to > its functionality. While trying to understand what it does I think it > is not working as it should. > > Here is the link: http://lsr.di.unimi.it/LSR/Item?id=744 > > M

Re: Q re LSR snippet 744

Am 19.03.2016 um 11:02 schrieb Michael Gerdau: Hi list, I'm playing with LSR snippet 744 and wish to make a small amendment to its functionality. While trying to understand what it does I think it is not working as it should. Here is the link: http://lsr.di.unimi.it/LSR/Item?id=744 Most import

Q re LSR snippet 744

Hi list, I'm playing with LSR snippet 744 and wish to make a small amendment to its functionality. While trying to understand what it does I think it is not working as it should. Here is the link: http://lsr.di.unimi.it/LSR/Item?id=744 Most importantly I think the words 'lil le' and 'fis ker' sh

Re: LSR search not working?

Harm, this looks promising! Cheers, Pierre 2016-02-09 17:17 GMT+01:00 Thomas Morley : > 2016-02-08 12:35 GMT+01:00 Pierre Perol-Schneider > : > > Now I see. Smart idea! > > > > Cheers, > > Pierre > > > > 2016-02-07 23:31 GMT+01:00 Thomas Morley : > >> > >> 2016-02-07 12:13 GMT+01:00 Pierre Perol-

Re: LSR search not working?

2016-02-08 12:35 GMT+01:00 Pierre Perol-Schneider : > Now I see. Smart idea! > > Cheers, > Pierre > > 2016-02-07 23:31 GMT+01:00 Thomas Morley : >> >> 2016-02-07 12:13 GMT+01:00 Pierre Perol-Schneider >> : >> > 2016-02-05 10:38 GMT+01:00 Thomas Morley : >> >> - Doc-tag is removed. The way the bass-

Re: LSR search not working?

Now I see. Smart idea! Cheers, Pierre 2016-02-07 23:31 GMT+01:00 Thomas Morley : > 2016-02-07 12:13 GMT+01:00 Pierre Perol-Schneider > : > > 2016-02-05 10:38 GMT+01:00 Thomas Morley : > >> - Doc-tag is removed. The way the bass-signs, "///a" etc, are done > >> feels more like a workaround. > >>

Re: LSR search not working?

2016-02-07 12:13 GMT+01:00 Pierre Perol-Schneider : > 2016-02-05 10:38 GMT+01:00 Thomas Morley : >> - Doc-tag is removed. The way the bass-signs, "///a" etc, are done >> feels more like a workaround. >> Not sure about it, though. Phil cc-ed, a second opinion would be nice. > > > This is definitel

Re: LSR search not working?

Hi Harm, 2016-02-05 10:38 GMT+01:00 Thomas Morley : > - I inserted a remark about use of newer devel-versions with it, at a > single detail. > Yep, good idea. > - Doc-tag is removed. The way the bass-signs, "///a" etc, are done > feels more like a workaround. > Not sure about it, though. Ph

Re: LSR search not working?

2016-02-05 7:30 GMT+01:00 Pierre Perol-Schneider : > Done. > Cheers, > Pierre > > 2016-02-04 23:45 GMT+01:00 Pierre Perol-Schneider > : >> >> OK I'll take a look at it tomorrow. >> Cheers, >> Pierre >> >> 2016-02-04 23:12 GMT+01:00 Thomas Morley : >>> >>> 2016-02-04 13:43 GMT+01:00 Pierre Perol-Sch

Re: LSR search not working?

Done. Cheers, Pierre 2016-02-04 23:45 GMT+01:00 Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com>: > OK I'll take a look at it tomorrow. > Cheers, > Pierre > > 2016-02-04 23:12 GMT+01:00 Thomas Morley : > >> 2016-02-04 13:43 GMT+01:00 Pierre Perol-Schneider >> : >> > Hi Nick, >> > >> > T

Re: LSR search not working?

OK I'll take a look at it tomorrow. Cheers, Pierre 2016-02-04 23:12 GMT+01:00 Thomas Morley : > 2016-02-04 13:43 GMT+01:00 Pierre Perol-Schneider > : > > Hi Nick, > > > > This snippet has not been approved yet. Therefor, it is not taken into > > account is the searching algorithm. > > Cheers, > >

Re: LSR search not working?

2016-02-04 13:43 GMT+01:00 Pierre Perol-Schneider : > Hi Nick, > > This snippet has not been approved yet. Therefor, it is not taken into > account is the searching algorithm. > Cheers, > Pierre > > 2016-02-04 12:16 GMT+01:00 Nick Payne : >> >> There is an LSR snippet for Baroque lute tablature at

  1   2   3   4   >