For days now I haven't been able to reach the Lilypond Snippet Repository at
http://lsr.di.unimi.it/LSR/
Is something going on??
--
Met vriendelijke groet,
Erik Appeldoorn
Hello David,
> But there’s got to be a way to access these properties, right? Or is the
\book
> (\bookpart, \score) context just not available?
I think the book header is not available at time of markup evaluation. What is
available is the paper-block via layout. So what we could do is
%%%
#(
>> Would it be possible to extend the markupWithHeaders function (from LSR 467:
>> http://lsr.di.unimi.it/LSR/Item?id=467) so that it included headers from the
>> \book level? The comments have a TODO to add the \score level headers.
>> What would it take to add hea
On 24/04/2025 04:29, David F. wrote:
Would it be possible to extend the markupWithHeaders function (from
LSR 467: http://lsr.di.unimi.it/LSR/Item?id=467) so that it included
headers from the \book level? The comments have a TODO to add the
\score level headers. What would it take to add
Would it be possible to extend the markupWithHeaders function (from LSR 467:
http://lsr.di.unimi.it/LSR/Item?id=467) so that it included headers from the
\book level? The comments have a TODO to add the \score level headers. What
would it take to add headers from \book and \bookpart and
Hi David,
> IIRC, that snippet originally had a different purpose than it does now; I
> think it began as a way to move each lyric syllable so that its first vowel
> is centered on the notehead. For a contrived example, it would move the
> syllable "Shhhow!" so that the o is centered under
Hello
There's a snippet at
https://lsr.di.unimi.it/LSR/Snippet?id=888
IIRC, that snippet originally had a different purpose than it does
now; I think it began as a way to move each lyric syllable so that
its first vowel is centered on the notehead. For a contrived
example, it would mov
Michael Gerdau wrote:
Hi Lilyponders,
I've played a bit with the expanded MetronomMark / approximate Tempo
marks as of LSR Snippet 869 and 1008.
https://lsr.di.unimi.it/LSR/Item?id=869
https://lsr.di.unimi.it/LSR/Item?id=1008
Both snippets won't work with neither 2.24.4 nor 2.25.23
Hi Lilyponders,
I've played a bit with the expanded MetronomMark / approximate Tempo
marks as of LSR Snippet 869 and 1008.
https://lsr.di.unimi.it/LSR/Item?id=869
https://lsr.di.unimi.it/LSR/Item?id=1008
Both snippets won't work with neither 2.24.4 nor 2.25.23.
Thre problem seem
> Also, I’m sure you didn’t mean it that way, but the improvement to
> the LSR snippet is worthwile regardless, I think.
Yep.
> Going to greater lengths though—while reading your code I wondered
> whether it wouldn’t make sense to go the step of not taking strings
> as arguments
Hi Werner,
On 13.07.24 06:36, Werner LEMBERG wrote:
I came across LSR #304https://lsr.di.unimi.it/LSR/Item?id=304 and I
think we should suggest a coding with variables there, like this:
[...]
Yes, LilyPond should be both more supportive and more 'user friendly'
here; this is
> I came across LSR #304 https://lsr.di.unimi.it/LSR/Item?id=304 and I
> think we should suggest a coding with variables there, like this:
> [...]
Yes, LilyPond should be both more supportive and more 'user friendly'
here; this is tracked as
https://gitlab.com/lilypond/lil
Hello,
I came across LSR #304 https://lsr.di.unimi.it/LSR/Item?id=304 and I
think we should suggest a coding with variables there, like this:
%%
startTrillSpanSharp =
-\tweak bound-details.left.text
\markup { \musicglyph "scripts.trill" \raise #0.65 \te
>> 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
> 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
The LSR looks like it's down. I don't know who is responsible for it so I
thought I'd just post here.
--
Knute Snortum
On 20.06.24 14:41, Jean Abou Samra wrote:
Done
Thanks!
> 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
Hello everyone,
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
Thanks in advance
Simon
To the author of the new LSR snippet 1187 "New pitch language"
https://lsr.di.unimi.it/LSR/Item?u=1&id=1187
You add your new language to "nederlands", thus
\language "alpha"
returns a warning:
warning: Could not find language `alpha'. Ignoring.
Please f
> I have some questions about the LSR and I hope this is the place to ask
> them.
>
> I have noticed that some snippets take up a lot of blank space under
> them. This is because they have marked the snippet as stand-alone,
> but haven't put a "tagline = ##f" i
I have some questions about the LSR and I hope this is the place to ask
them.
I have noticed that some snippets take up a lot of blank space under them.
This is because they have marked the snippet as stand-alone, but haven't
put a "tagline = ##f" in the paper or header block. I&
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, Knu
> 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.
It looks like https://lsr.di.unimi.it/ is down. Does anyone know who
administers that site?
--
Knute Snortum
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
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 syllable but the last in a word doesn’t have point-and-click the
way it is
>> Any idea how this can be fixed?
>
> Fixed in LSR (hint: `#(debug-enable 'backtrace)` helps in such
> cases).
That was fast, thanks!
Werner
Le jeudi 13 avril 2023 à 19:26 +, Werner LEMBERG a écrit :
> ```
>
> After inserting a version statement and running `convert-ly` on
>
>
> [http://lsr.di.unimi.it/LSR/Item?id=1000](http://lsr.di.unimi.it/LSR/Item?id=1000)
>
> I get this ominous error:
>
After inserting a version statement and running `convert-ly` on
http://lsr.di.unimi.it/LSR/Item?id=1000
I get this ominous error:
```
init.ly:64:2: error: Guile signaled an error for the expression beginning here
#
(let ((book-handler (if (defined? 'default-toplevel-book-handle
On 12/30/2021 3:12 PM, Dan Eble wrote:
MarkEvent was split into RehearsalMarkEvent and AdHocMarkEvent in the summer of
2021. You might try replacing MarkEvent with AdHocMarkEvent and see whether it
works for you.
LilyPond 2.23.6 will support some D.C., D.S., al Fine, and alla Coda repeat stru
On Dec 30, 2021, at 14:24, Lukas-Fabian Moser wrote:
>
> Hi Joel,
>
>> Several of the scores used poly-mark-engraver from
>> <https://lsr.di.unimi.it/LSR/Item?id=976> (see also
>> <https://lists.gnu.org/archive/html/lilypond-user/2011-08/msg00157
er, and I’m running 2.23.5 on Windows 11.
>
> Several of the scores used poly-mark-engraver from
> <https://lsr.di.unimi.it/LSR/Item?id=976> (see also
> <https://lists.gnu.org/archive/html/lilypond-user/2011-08/msg00157.html>),
> and this now fails with
>
Hi Joel,
Several of the scores used poly-mark-engraver from
<https://lsr.di.unimi.it/LSR/Item?id=976> (see also
<https://lists.gnu.org/archive/html/lilypond-user/2011-08/msg00157.html>),
and this now fails with
fatal error: cannot find music object: MarkEvent
(Minimal e
I'm returning to an old project (last touched in 2016) on a new
computer, and I’m running 2.23.5 on Windows 11.
Several of the scores used poly-mark-engraver from
<https://lsr.di.unimi.it/LSR/Item?id=976> (see also
<https://lists.gnu.org/archive/html/lilypond-user/2011-08
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/L
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 speaks up I'll delete it soon.
Cheers,
Harm
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 s
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 simply
adjusting some other stuff?
Leading to:
\version "2.
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 simply
adjusting some other stuff?
Leading to:
\version "2.
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&
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 descripti
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
>
>
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.
> >
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 \over
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
I’m trying to sign-up for the LSR in order to contribute a snippet. However,
even though I apparently successfully complete the “New element” form, I remain
unable to login. Is there some sort of lag in when registrations become active
or is there some other problem going on?
✝✝✝
compiles at least locally.
>
> Regards,
> Valentin
Hi Valentin,
the LSR currently runs 2.18.2.
Upgrading it to 2.20.0 is on TODO.
Thanks,
Harm
Hello,
While I cannot help you with this, I noticed that this snippet must have been
done in an older version of lilypond, thus it uses older music function calls.
I’ve updated the snippet to 2.20, so now it compiles at least locally.
Regards,
Valentin%% LSR originally contributed by Gilles
On Mon, Jun 29, 2020 at 2:59 PM Thomas Morley
wrote:
> Am Sa., 20. Juni 2020 um 17:18 Uhr schrieb Ralph Palmer
> :
> >
> > On Sat, Jun 20, 2020 at 6:28 AM Karlin High
> wrote:
> >>
> >> On 6/20/2020 7:37 AM, Thomas Morley wrote:
> >
Am Sa., 20. Juni 2020 um 17:18 Uhr schrieb Ralph Palmer
:
>
> On Sat, Jun 20, 2020 at 6:28 AM Karlin High wrote:
>>
>> On 6/20/2020 7:37 AM, Thomas Morley wrote:
>> > I'd say we need more people for LSR-work.
>> >
>> > Furthermore, some time ago
Hi,
said snippet waits to be approved.
Alas, I think it will never work in the jail the lsr is running in.
Could someone with experience in running LilyPond in a jail could have
a look at the code:
https://lsr.di.unimi.it/form.php?type=snippet;id=;rld=m_snippet
?
Thanks,
Harm
On Sat, Jun 20, 2020 at 6:28 AM Karlin High wrote:
> On 6/20/2020 7:37 AM, Thomas Morley wrote:
> > I'd say we need more people for LSR-work.
> >
> > Furthermore, some time ago I started to upgrade LSR to 2.20, but had
> > to stop this work as well.
> &
On 6/20/2020 7:37 AM, Thomas Morley wrote:
I'd say we need more people for LSR-work.
Furthermore, some time ago I started to upgrade LSR to 2.20, but had
to stop this work as well.
No idea, when I'm able to continue...
Can the work be described in step-by-step instructions? If so
Am Fr., 19. Juni 2020 um 22:57 Uhr schrieb Valentin Villenave
:
>
> On 6/19/20, Lukas-Fabian Moser wrote:
> The LSR is only tended to by “Thomas Morley” and myself these days
> (and unlike him, I am doing a lousy job of it),
Well, I can't say I'm doing it better.
In times
On 6/19/20, Lukas-Fabian Moser wrote:
> But this seems not to have been taken up for the database, neither as an
> addition nor as a replacement for 792 (see
> http://lsr.di.unimi.it/LSR/Search?q=clef+change).
> Did I do something wrong?
No, you did everything right (TBH, you cou
Folks,
some months ago I tried to improve an LSR snippet
(http://lsr.di.unimi.it/LSR/Item?id=792 "Clef change at the beginning of
a piece"); namely, I added support for the use of key signatures which
the original LSR solution messes up (*).
Following the instruction
> I doubt it's caused by any custom-engraver.
> At least on my machine this code:
>
> \paper {
> systems-per-page = #5
> }
>
> music = \absolute {
> \repeat unfold 2000 {
> d'8 f' a' g' d' f' b' d' d'8 f' a' g' d' f' b' d' \break
> }
> }
>
> \new Staff { \music }
>
> already f
Am Mi., 8. Apr. 2020 um 16:13 Uhr schrieb Michael Gerdau :
>
> Hi Kieren,
>
> >> I'm playing with the bars-per-line-engraver as of LSR
> >> http://lsr.di.unimi.it/LSR/Item?id=838
> >>
> >> When I increase the number of bars in my piece beyond a
Hi Kieren,
>> I'm playing with the bars-per-line-engraver as of LSR
>> http://lsr.di.unimi.it/LSR/Item?id=838
>>
>> When I increase the number of bars in my piece beyond a certain amount
>> (3500-4000 in my MWE) lilypond crashes with an access violation unde
Hi Michael,
> I'm playing with the bars-per-line-engraver as of LSR
> http://lsr.di.unimi.it/LSR/Item?id=838
>
> When I increase the number of bars in my piece beyond a certain amount
> (3500-4000 in my MWE) lilypond crashes with an access violation under linux.
Does that al
I can confirm the segmentation fault in the "Drawing systems" phase,
using 2.20.0 in Ubuntu.
/Mats
On 2020-04-08 09:41, Michael Gerdau wrote:
Hi list,
I'm playing with the bars-per-line-engraver as of LSR
http://lsr.di.unimi.it/LSR/Item?id=838
When I increase the numbe
Hi list,
I'm playing with the bars-per-line-engraver as of LSR
http://lsr.di.unimi.it/LSR/Item?id=838
When I increase the number of bars in my piece beyond a certain amount
(3500-4000 in my MWE) lilypond crashes with an access violation under linux.
I have this problem with both 2.19.8
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 upda
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
n inside the description or as snippet output?
> > Btw, do you know a way to dump warning-messages to the graphical output?
> Added some examples to the description.
> The LSR seems to be down at the moment, though.
> What bothers me a little bit is the unpredictable order of warn
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
about gving the user some hint or example-message what can be
expected if warnings are triggered or debug-mode is enabled?
Do you mean inside the description or as snippet output?
Btw, do you know a way to dump warning-messages to the graphical output?
Added some examples to the description.
The LSR
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
ings. ;)
>
> I did substantially rework some parts of the engraver, namely switching
> to a list-processing-way of dealing with current/last-grobs/pitches/...
> Not sure if you like this change. I like it for less code duplication...
Fine with me, I already updated the LSR-code, for now unapproved.
ode.
Other hooks should be thoroughly demonstrated, _if_ they are needed to
get the desired result.
In other words, demonstrating process-acknowledged should be left to
another LSR snippet.
Ok.
Btw, there is one case, where I don't know how to deal with:
2.18.2 can't cope wi
p downp))
> #:vcenter ")" )
>
> --
> Dave Higgins
Hi Dave,
I've applied your suggestion.
http://lsr.di.unimi.it/LSR/Item?id=782
Thanks,
Harm
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 down upp downp) grob)
(grob-interpret-markup grob
(markup #:ove
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 {
<<
rob has been acknowledged by the engraver. The question is to which
> extent
> the "educational" idea of showing the various hooks in action justifies
> this overhead.
I think we should go for the current code.
Other hooks should be thoroughly demonstrated, _if_ they are needed
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
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
chrieb Thomas Morley:
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 no
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 is in, it has to be reviewed and a
:
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:
"
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
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
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 databas
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 is in, it has to be reviewed and approved
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...
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 t
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 what a valuable
resource it is?
Andrew
, PN Morin <_...@live.com> wrote:
>
> Hello all,
>
> Hmm, hopefully temporary ?
>
> The LSR is supposed to be hosted by the Università di Milano la Statale,
> according to the domain name. Probably deployed by a music professor there
> once upon a time? @Urs Liska
Hello all,
Hmm, hopefully temporary ?
The LSR is supposed to be hosted by the Università di Milano la Statale,
according to the domain name. Probably deployed by a music professor there once
upon a time? @Urs Liska<mailto:u...@openlilylib.org> any clue?
The whois entry yields this:
In the meantime, The Wayback machine has snapshots:
https://web.archive.org/web/20190510220444/http://lsr.di.unimi.it/LSR/Browse
I think the search functionality is broken, though.
On Sat, 16 Nov 2019 at 09:39, Manuela wrote:
> Do you know who owns LSR?
>
> Greetings,
Do you know who owns LSR?
Greetings,
Manuela
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
Same with me 1:01 pm PST
Mark
-Original Message-
From: lilypond-user
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
Aaron Hill
Sent: Friday, November 15, 2019 12:18 PM
To: lilypond-user@gnu.org
Subject: Re: Has LSR moved?
On 2019-11-15 11:39 am, David Sumbler
Am Fr., 15. Nov. 2019 um 20:40 Uhr schrieb David Sumbler :
>
> Has the Lilypond Snippets Repository moved?
>
> The address I have bookmarked, http://lsr.di.unimi.it/LSR/Search ,
> gives me a "Not Found" error.
>
> David
Yesterday it worked, now I get the
On 2019-11-15 11:39 am, David Sumbler wrote:
Has the Lilypond Snippets Repository moved?
The address I have bookmarked, http://lsr.di.unimi.it/LSR/Search ,
gives me a "Not Found" error.
How peculiar. I just used the site earlier this morning. And I am now
also getting the
Has the Lilypond Snippets Repository moved?
The address I have bookmarked, http://lsr.di.unimi.it/LSR/Search ,
gives me a "Not Found" error.
David
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
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 so
Replied off-list.
--
Phil Holmes
- Original Message -
From: "Aaron Hill"
To:
Sent: Friday, June 07, 2019 1:18 PM
Subject: Re: DNS issues with LSR
On 2019-06-07 2:54 am, Aaron Hill wrote:
Hi folks,
Who is the contact point for the LSR, more specifically the
On 2019-06-07 2:54 am, Aaron Hill wrote:
Hi folks,
Who is the contact point for the LSR, more specifically the individual
responsible for their DNS?
There has been a long-standing issue with their name servers that
prevent services like CloudFlare from reliably resolving records.
This is
Hi folks,
Who is the contact point for the LSR, more specifically the individual
responsible for their DNS?
There has been a long-standing issue with their name servers that
prevent services like CloudFlare from reliably resolving records. But
now things are worse, and it seems that
1 - 100 of 715 matches
Mail list logo
