Hi Andrew,
> Since handing over OLL I have lost track of processes. What is the
> communications platform for queries and discussions now?
This mailing list seems best.
> And are we in fact still open for business? I need to submit a pull
> request to add some code for my slash stem functions
Are we taking pull requests. Sorry my metaphor may not have been clear!
On 7 April 2023 10:17:51 pm AEST, Jean Abou Samra wrote:
>
>
>> Le 7 avr. 2023 à 14:06, Andrew Bernard a écrit :
>>
>> Since handing over OLL I have lost track of processes. What is the
>> communications platform for
> Le 7 avr. 2023 à 14:06, Andrew Bernard a écrit :
>
> Since handing over OLL I have lost track of processes. What is the
> communications platform for queries and discussions now?
I don’t think anything has been set up to replace your Discourse server, but
GitHub issues are still there.
Since handing over OLL I have lost track of processes. What is the
communications platform for queries and discussions now? And are we in
fact still open for business? I need to submit a pull request to add
some code for my slash stem functions which somehow never made it in.
Andrew
ones more easily.)
https://github.com/orgs/openlilylib/repositories
As I mentioned a while ago I would like to convert the oldest one to an
"entry-point" to help with visibility - see
https://github.com/openlilylib/openlilylib/pull/1
Unfortunately I don't have any rights over
I seem to have become completely detached from OLL.
Where is the repository located now? The only repos I can find are last
modified 6-10 years ago.
Andrew
Le 23/11/2022 à 16:31, Graham King a écrit :
>>> I've tried to get Scholarly working in the past, but failed. I'm currently
>>> failing to get lyluatex working.
>>> There are some really promising tools in OpenLilyLib, but they seem to
>>> require someone with Urs' l
giorno mer 23 nov 2022 alle 17:55:34 +0100, Jean Abou Samra
ha scritto:
Le 23/11/2022 à 16:31, Graham King a écrit :
I've tried to get Scholarly working in the past, but failed. I'm
currently failing to get lyluatex working.
There are some really promising tools in OpenLilyLib, but they seem
Le 23/11/2022 à 16:31, Graham King a écrit :
I've tried to get Scholarly working in the past, but failed. I'm currently
failing to get lyluatex working.
There are some really promising tools in OpenLilyLib, but they seem to require
someone with Urs' level of focus and intellect to use them
holarly working in the past, but failed. I'm currently
failing to get lyluatex working.
There are some really promising tools in OpenLilyLib, but they seem to require
someone with Urs' level of focus and intellect to use them. This thread is
raising my hopes once more.
Hello Mark,
> Yes, I think we all agree on that. At the moment there isn't, but even
> if and when that might be implemented, I can still see a role for a
> repository such as OpenLilyLib to collect and host those modules. Is the
> future really copying blocks of code from websi
Le 22/11/2022 à 08:50, Henning Hraban Ramm a écrit :
... module code ...
\endModule % or whatever name
... example ...
where \endModule would act as a "trap" interrupting the parsing,
but only if the file is included. If the file is compiled as
main, it would continue parsing, and after
Mark, I use my stem slash code a lot.
I don't think you should delete things willy nilly. There may be users
who use stuff in OLL that do not respond in the list etc etc.
Andrew
here isn't, but even
if and when that might be implemented, I can still see a role for a
repository such as OpenLilyLib to collect and host those modules. Is the
future really copying blocks of code from websites or email attachments
and saving them to randomly organized local files?
In the meantime, O
Am 21.11.22 um 23:28 schrieb Jean Abou Samra:
One would add a new keyword in the parser akin to \include
(\import? \load?).
How about \require?
... module code ...
\endModule % or whatever name
... example ...
where \endModule would act as a "trap" interrupting the parsing,
but only if
On Mon, Nov 21, 2022, 6:11 PM Andrew Bernard
wrote:
> it costs money for me to run the server
>
What storage and RAM is needed?
I might be able to host it for you.
--
Karlin High
Missouri, USA
>
I may as well shutdown openlilylib.space then. There are only 15 users,
and it costs money for me to run the server, and there is zero traffic
on Discourse.
Andrew
On 22/11/2022 9:22 am, Jean Abou Samra wrote:
Le 21/11/2022 à 23:19, Andrew Bernard a écrit :
Hello All,
Why don't we keep
Hi Jean,
> I would change the tense:
>
> [Independently of OLL,] non core developers *are* able to implement
> new features with Scheme code that *can* potentially be included in
> base LilyPond if proven reasonable.
>
> Don't you agree?
I do agree that users are able to implement feature with
Hi Jean,
> The first step to adding non-trivial things that need discussion
> is opening an issue. Do you feel like doing that?
https://gitlab.com/lilypond/lilypond/-/issues/6475
Look at me, being all “Do first” ’n’ stuff… ;)
We taking the discussion over there?
K
Le 21/11/2022 à 23:02, Kieren MacMillan a écrit :
Then they should definitely be added: those were things Urs and I discussed (a
fair bit off-list) as principle obstacles to the integration of “external” code
(mostly equivalent to OLL at the time) into the ’Pond ecosystem.
The first step to
Le 21/11/2022 à 23:19, Andrew Bernard a écrit :
Hello All,
Why don't we keep the discussion about OLL on the OLL Discourse forum
I created and run? That's the whole point of it, and to avoid
cluttering the Lilypond User list.
I think Mark's goal was to reach LilyPond users who are only
are welcome.
Andrew
On 22/11/2022 4:09 am, Mark Knoop wrote:
With the imminent release of LilyPond 2.24, I thought it would be good
to (once again) raise the topic of OpenLilyLib.
how much this resource isused
>
> I have heard lots of good things about OpenLilyLib.
>
> But I remain somewhat unclear as to what it offers and how it would be
> used in my usages for SATB/TTBB shape-note hymns and light choral works.
>
> My first experience with OLL was downloading
Hi all,
> I don't think we're very far from that. Include files already work
> as kinds of modules. I only see two potential differences between modules
> and include files:
>
> - a module should only be loaded once, even if imported twice in
> different locations,
>
> - a module could
Le 21/11/2022 à 22:38, Valentin Petzel a écrit :
In my opinion it is not bad to allow for modular extension of Lilypond,
especially for things that do not fit the core of the program. You need to keep
in mind that this would be a strong possibility of enhancing Lilypond without
cluttering it’s
loping
> openLilyLib as a library external to LilyPond, as opposed to
> contributing features to LilyPond itself, was supposed to be.
>
> I was going to add my lyrics code to LSR, actually. It's just
> more convenient for users to grab, and it's not like this is
> a very large piece o
Le 21/11/2022 à 21:55, Kieren MacMillan a écrit :
cf. our past discussions (some on -devel, some private) about my attempts to
add code, where it should go, etc.
=)
Yes, I remember that :-)
2. Obviously I use oll-core, since that is foundational to the EE.
Note: oll-core is a
Hi all,
> Maybe what I'm going to say will sadden some, but personally,
> I never quite understood what the advantage of developing
> openLilyLib as a library external to LilyPond, as opposed to
> contributing features to LilyPond itself, was supposed to be.
cf. our past discu
On 11/21/2022 11:09 AM, Mark Knoop wrote:
It would be good to get a feel from users how much this resource isused
I have heard lots of good things about OpenLilyLib.
But I remain somewhat unclear as to what it offers and how it would be
used in my usages for SATB/TTBB shape-note hymns
Le 21/11/2022 à 20:02, Mark Knoop a écrit :
Thanks Jean for your thoughts, which are not so far from my own. A few comments:
Maybe what I'm going to say will sadden some, but personally,
I never quite understood what the advantage of developing
openLilyLib as a library external to LilyPond
Thanks Jean for your thoughts, which are not so far from my own. A few comments:
> Maybe what I'm going to say will sadden some, but personally,
> I never quite understood what the advantage of developing
> openLilyLib as a library external to LilyPond, as opposed to
> contribut
Maybe what I'm going to say will sadden some, but personally,
I never quite understood what the advantage of developing
openLilyLib as a library external to LilyPond, as opposed to
contributing features to LilyPond itself, was supposed to be.
I was going to add my lyrics code to LSR, actually
With the imminent release of LilyPond 2.24, I thought it would be good
to (once again) raise the topic of OpenLilyLib. There has been some
recent movement on this (thanks to Jean and Andrew) to get the code
mostly working with recent LilyPond versions and Guile 2.
I have also just pushed a bunch
Hi Mark,
thank you! Due to a change in work, I haven't gotten around to testing
your changes in depth yet, but I assume that as an OLL user, you've
solved the problems so that it works. When I have it running here, I may
approach you with a call for a pull request.
Best
Jan-Peter
Am 17.07.22
At 15:56 on 17 Jul 2022, Mark Knoop wrote:
I note a bug with the edition-engraver which can no longer address the
first moment of the score. This needs further investigation (unless
somebody else has already solved this?).
Further to this, I've just pushed a fix for the first moment bug to my
Hi Andrew and other OLL users,
At 18:24 on 27 May 2022, Andrew Bernard wrote:
The upshot of that is that I suppose I should revive the OLL work. I'll
recreate the dedicated server I set up, recreate the Discourse forum for
discussion, and work on the git repository, then people can
Le 06/06/2022 à 13:00, Andrew Bernard a écrit :
Not exactly just fork . The use of an organisation in github is
important I believe. I suppose it is silly but I wanted the name
openlilylib for the org, and also to preserve all the users etc,
but now it will have to be oll.
How about
Not exactly just fork . The use of an organisation in github is
important I believe. I suppose it is silly but I wanted the name
openlilylib for the org, and also to preserve all the users etc,
but now it will have to be oll.
Andrew
Jean Abou Samra wrote on 6/06/2022 8:47 PM:
Well, I guess
Le 06/06/2022 à 07:35, Andrew Bernard a écrit :
Yes, I already wrote to him. No reply and no bounce. So I can see who
the owners are from github, but asking if they are still on here.
Well, I guess the way to go for you is to fork OLL at this point.
Yes, I already wrote to him. No reply and no bounce. So I can see who
the owners are from github, but asking if they are still on here.
Andrew
Jean Abou Samra wrote on 6/06/2022 3:18 PM:
Le 06/06/2022 à 05:01, Andrew Bernard a écrit :
From https://github.com/orgs/openlilylib/people
Le 06/06/2022 à 05:01, Andrew Bernard a écrit :
Are any of the owners of the openlilylib github organisation still on
this list? If so, could they please contact me as I am trying to
revive the OLL project.
From https://github.com/orgs/openlilylib/people,
it looks like that may be Janek
Are any of the owners of the openlilylib github organisation still on
this list? If so, could they please contact me as I am trying to revive
the OLL project.
Andrew
I've recreated a server to run a portal site for OpenLilyLib project and
related topics.
https://openlilylib.space/
I'll be making the Discourse server today, for OLL specific discussion
and support.
Also, I'll be providing access and support for the OLL repository on
GitHub, which
I've created a new server to run a portal site for OpenLilyLib project
and related topics.
https://openlilylib.space/
I'll be making the Discourse server today, for OLL specific discussion
and support.
Also, I'll be providing access and support for the OLL repository on
GitHub, which
forum (or I forgot).
Thanks,
Peter
--
Peter Crighton | Musician & Music Engraver based in Mainz, Germany
https://www.petercrighton.de
On Fri, 27 May 2022 at 10:28, Andrew Bernard
wrote:
> Hello All,
>
> Having had to abandon the Openlilylib (OLL) work I took over from Urs
> Li
, Andrew Bernard wrote:
Hello All,
Having had to abandon the Openlilylib (OLL) work I took over from Urs
Liska, for various reasons, in the meantime I went over to Dorico
instead of Lilypond for my work. Having spent a lot of money on Dorico
(AUD$800+) and given it my best shot for more than year
a differing opinion.
David
From: lilypond-user
on behalf of Andrew Bernard
Date: Friday, May 27, 2022 at 4:26 AM
To: lilypond-user@gnu.org
Subject: Openlilylib
Hello All,
Having had to abandon the Openlilylib (OLL) work I took over from Urs
Liska, for various reasons, in the meantime I went
o abandon the Openlilylib (OLL) work I took over from Urs
> Liska, for various reasons, in the meantime I went over to Dorico
> instead of Lilypond for my work. Having spent a lot of money on Dorico
> (AUD$800+) and given it my best shot for more than year, it really falls
> short for the
Hello All,
Having had to abandon the Openlilylib (OLL) work I took over from Urs
Liska, for various reasons, in the meantime I went over to Dorico
instead of Lilypond for my work. Having spent a lot of money on Dorico
(AUD$800+) and given it my best shot for more than year, it really falls
downloaded from Urs's site? Would you be willing to share it with
me?
Thanks,
Carl
On Mon, May 9, 2022 at 1:54 AM Andrew Bernard
wrote:
> Hello All,
>
> I've been absent from the list for a long time, but recently got CC'd
> about an Openlilylib pull request.
>
> I must apologise
Hi Andrew,
thanks for the information. Sorry to hear about your illness and all the
best wishes nonetheless!
Best,
Simon
On 09/05/2022 09:53, Andrew Bernard wrote:
Hello All,
I've been absent from the list for a long time, but recently got CC'd
about an Openlilylib pull request.
I must
On Mon, May 9, 2022 at 12:55 AM Andrew Bernard
wrote:
> Hello All,
>
> I've been absent from the list for a long time, but recently got CC'd
> about an Openlilylib pull request.
>
> I must apologise for never getting around to updating the list on the
> Openlilylib project
. The very quality of core LilyPond may
be the reason why packaging layers around it have failed to really
take off and LSR remains far more commonly used than openLilyLib.
Not to mention that many amazing LilyPond snippets are expressed
in less than 50 lines of Scheme code, which is just as convenient
Am 09.05.22 um 01:59 schrieb David Kastrup:
The "TeX ecosystem" consists of plain TeX with fudge-ons (comparable to
LilyPond and LSR snippets), of the monolithic Context (driven by a
not-much-more-than-one-man company), and of the modular LaTeX. The only
system that has exploded in number and
Hello All,
I've been absent from the list for a long time, but recently got CC'd
about an Openlilylib pull request.
I must apologise for never getting around to updating the list on the
Openlilylib project status. Some time ago I took over from Urs who is no
longer able to do the work
Simon Albrecht writes:
> On 08/05/2022 20:37, Jean Abou Samra wrote:
>> The case study of how OLL fell out of maintenance is one of the
>> things leading me to think that a model where snippets providing
>> significant functionality and becoming somewhat popular get
>> upstreamed into the
On 08/05/2022 20:37, Jean Abou Samra wrote:
The case study of how OLL fell out of maintenance is one of the
things leading me to think that a model where snippets providing
significant functionality and becoming somewhat popular get
upstreamed into the LilyPond core is a better fit for LilyPond
Le 08/05/2022 à 20:37, Jean Abou Samra a écrit :
Le 08/05/2022 à 20:08, Simon Albrecht a écrit :
Dear community,
I have made some small updates to keep the openlilylib/bezier module
working with current versions of LilyPond and created a pull request
on GitHub. Is anyone currently able
Le 08/05/2022 à 20:08, Simon Albrecht a écrit :
Dear community,
I have made some small updates to keep the openlilylib/bezier module
working with current versions of LilyPond and created a pull request
on GitHub. Is anyone currently able to notice and approve the request?
I don't think so
Dear community,
I have made some small updates to keep the openlilylib/bezier module
working with current versions of LilyPond and created a pull request on
GitHub. Is anyone currently able to notice and approve the request?
Best, Simon
Dear list,
> >
> > I have started using the experimental 2.23.5 build with Guile 2.2 [1]
> > and it turns out to be incompatible with the core of openLilyLib.
> >
> > Here are the error messages I got—it may be that only the first is
> > relevant:
> >
Le 19/01/2022 à 01:45, Jean Abou Samra a écrit :
Le 18/01/2022 à 20:43, Simon Albrecht a écrit :
Dear list,
I have started using the experimental 2.23.5 build with Guile 2.2 [1]
and it turns out to be incompatible with the core of openLilyLib.
Here are the error messages I got—it may
Le 18/01/2022 à 20:43, Simon Albrecht a écrit :
Dear list,
I have started using the experimental 2.23.5 build with Guile 2.2 [1]
and it turns out to be incompatible with the core of openLilyLib.
Here are the error messages I got—it may be that only the first is
relevant:
[...]
Take
Dear list,
I have started using the experimental 2.23.5 build with Guile 2.2 [1]
and it turns out to be incompatible with the core of openLilyLib.
Here are the error messages I got—it may be that only the first is relevant:
%%
/home/simon/openlilylib/oll-core/internal
https://github.com/openlilylib/oll-core/issues/62
On 18/01/2022 20:43, Simon Albrecht wrote:
I have started using the experimental 2.23.5 build with Guile 2.2 [1]
and it turns out to be incompatible with the core of openLilyLib.
Here are the error messages I got—it may be that only the first
Thank you all for the supportive comments. They are more than
sufficient justification to make it worthwhile to continue.
I better knuckle down and reincarnate the website, the Discourse
forum, and finally do the git repository refactoring. I set up a new
server already.
Andrew
Hi Andrew,
> nobody has noticed the loss of the website or forum,
> which did have a few members,
> so I wonder if this is worth pursuing anyway.
+1 to everything Carl wrote.
Here’s a little more personal perspective…
I freely admit that I didn’t notice the loss of the website or forum. There
ne person.
>
> Best
>
> Damian
>
>
>
> > On 10 Mar 2021, at 22:21, Andrew Bernard
> wrote:
> >
> > Hello All,
> >
> > Some time ago I took over the management of the Openlilylib project from
> Urs Liska, who was forced to cease the
the management of the Openlilylib project from Urs
> Liska, who was forced to cease the work for personal reasons. I created a
> server to host a new website, a Git repository and a Discourse forum and
> Openlilylib specific mailing list. The old git repository remains untouched,
> but it is no lon
Andrew,
I would love to get to grips with Openlilylib (specifically, scholarLy) but
when I tried to register to its new home when you first announced it, I
couldn't get in. Can't remember the precise details now, and there wasn't time
to pursue it back then. But I suspect there might
On 3/10/21, 3:21 PM, "lilypond-user on behalf of Andrew Bernard"
wrote:
Hello All,
Some time ago I took over the management of the Openlilylib project from
Urs Liska, who was forced to cease the work for personal reasons. I
created a server to host a new webs
Hello All,
Some time ago I took over the management of the Openlilylib project from
Urs Liska, who was forced to cease the work for personal reasons. I
created a server to host a new website, a Git repository and a Discourse
forum and Openlilylib specific mailing list. The old git repository
Hello again,
I got a few private responses to this post — which were appreciated — but was
really hoping to get a discussion going about how such a system could be
implemented.
Perhaps the word “collaborator(s)” in the subject is too strong and scary? ;)
To be clear: my “problem” is never
In your debt, Andrew,
Ralph
On Thu, Oct 15, 2020 at 9:31 PM Andrew Bernard
wrote:
> What's happening with OLL, latest news. I have made a dedicated
> website, https://openlilylib.space.
>
--
Ralph Palmer
Brattleboro, VT
USA
(he, him, his)
palmer.r.vio...@gmail.com
toring, soonish.
>
> And by popular demand, I have corrected the capitalization of openLilyLib. :-)
>
> Andrew
>
item. No criticism of the existing
structure, but I think that just grew. I'll provide the GitLab details
when I have done the refactoring, soonish.
And by popular demand, I have corrected the capitalization of openLilyLib. :-)
Andrew
> Am 10.10.2020 um 17:49 schrieb Andrew Bernard :
>
> There's a term for it. Necroposting! Seriously!
I’m proud of my necromancer badge on stackexchange ;D
HR
There's a term for it. Necroposting! Seriously!
Andrew
On Sun, 11 Oct 2020 at 02:24, David Kastrup wrote:
> Two weeks? I've replied on occasion to threads that were 10 years old,
> basically because threads tends to be archived and turn up on keyword
> searches.
Simon Albrecht writes:
>> On 10.10.20 14:11, Simon Albrecht wrote:
>>> Dear Karsten and list,
>>>
>>> On 22.09.20 22:40, Karsten Reincke wrote:
5) I've learned, that all(?) of you consider this an untenable if
not silly position and that the PDFs and midi-files compiled by
There’s no such thing as retracting an e-mail, but I would like to do it.
Sorry for failing to realise how old the thread was before replying.
Best, Simon
On 10.10.20 14:11, Simon Albrecht wrote:
Dear Karsten and list,
On 22.09.20 22:40, Karsten Reincke wrote:
5) I've learned, that all(?) of
Simon Albrecht writes:
> Dear Karsten and list,
>
> On 22.09.20 22:40, Karsten Reincke wrote:
>> 5) I've learned, that all(?) of you consider this an untenable if
>> not silly position and that the PDFs and midi-files compiled by
>> Lilypond are never affected by the strong copyleft effect of
Dear Karsten and list,
On 22.09.20 22:40, Karsten Reincke wrote:
5) I've learned, that all(?) of you consider this an untenable if not
silly position and that the PDFs and midi-files compiled by Lilypond
are never affected by the strong copyleft effect of the GPL. That's
good to hear. But I
Since Urs has stepped down for personal reasons, I am willing to
continue the maintenance and development of OLL, as well as promotion
and improvement of documentation and information.
My understanding (perhaps incorrect) is that the Github repo is now
orphaned. I propose to create and manage a
Le 07/10/2020 à 16:30, Federico Bruni a écrit :
Il giorno mer 7 ott 2020 alle 16:24, Jean Abou Samra
ha scritto:
PPS: I see you shut down openlilylib.org. Is the source archived
somewhere
so I can better understand openLilyLib?
I think it's here:
https://github.com/openlilylib
Il giorno mer 7 ott 2020 alle 16:24, Jean Abou Samra
ha scritto:
PPS: I see you shut down openlilylib.org. Is the source archived
somewhere
so I can better understand openLilyLib?
I think it's here:
https://github.com/openlilylib-documentation/main-site/
Well, despite two of today's statements arguing otherwise I must say I
have come to a different conclusion. I have given myself exactly two
weeks to make a determination, and I realized I have obviously
overestimated the value and impact of my pet project openLilyLib. The
two weeks until
Am 07.10.20 um 02:18 schrieb Andrew Bernard:
> Urs and all,
>
> What happens to orphaned git repos? Not a case I am familiar with.
>
> I'd be happy to fork the OLL repo and take over the management and
> development. Should I do that? Are you going to delete the existing
> repo?
>
> Andrew
>
Hi
Urs and all,
What happens to orphaned git repos? Not a case I am familiar with.
I'd be happy to fork the OLL repo and take over the management and
development. Should I do that? Are you going to delete the existing
repo?
Andrew
Urs, I am unable to email you at openlilylib.org. Is there another way
to contact you off list?
Andrew
for Android<https://aka.ms/ghei36>
From: lilypond-user
on behalf of Andrew Bernard
Sent: Tuesday, October 6, 2020 5:18:03 PM
To: lilypond-user@gnu.org
Subject: Re: Future of openLilyLib
Urs,
I don't follow. Are you taking down OLL? There are surely many who
obviously
overestimated the value and impact of my pet project openLilyLib.
Well, despite two of today's statements arguing otherwise I must say I
have come to a different conclusion. I have given myself exactly two
weeks to make a determination, and I realized I have obviously
overestimated the value and impact of my pet project openLilyLib. The
two weeks until yesterday
\reshape is nice! I would try to make it clear in the documentation, if
\reshape is included in the core, that \shape is the legacy form to be
eventually deprecated and replaced by \reshape. Syntactically, it makes no
sense to have both functions available for the same thing. If there could be
>> \reshape ?
>
> Dude… nice work. =)
Care to submit a MR?
Werner
On 10/6/2020 11:23 AM, Kieren MacMillan wrote:
\reshape ?
Dude… nice work. =)
Made me smile, too. I think that's approaching the perfect amount of
self-reference humor, without crossing the line to guaranteed obscurity
for newcomers.
--
Karlin High
Missouri, USA
> \reshape ?
Dude… nice work. =)
Kieren.
Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: kie...@kierenmacmillan.info
On 2020-10-06 8:45 am, Carl Sorensen wrote:
If \shapeII is production ready, then I'm OK with adding it. But is
should
NOT be named \shapeII when it goes into core. It should be something
like
\shapeControl. \shapeII reflects the history that it came after the
creation of \shape. \shape
On Tue, Oct 6, 2020 at 8:43 AM Andrew Bernard
wrote:
> Hi JanPeter,
>
>
>
> One thing that concerns me with lilypond at the present is what I see
> as a sort of balkanisation of code. We have LSR, OLL, and people
> making one-shot GIT repos, and it's all very fragmented. I don't think
> this
Hi JanPeter,
I have contributed a bit to OLL and its machinery and I think it is an
important and indeed necessary resource. I am not sure why the uptake
is so limited, but I think somehow we have to communicate how easy it
is to install and use more effectively.
One thing that concerns me with
free to contact me via this list or py pm.
Best,
Jan-Peter
Am 21.09.20 um 17:24 schrieb Urs Liska:
> Hi all,
>
> to begin with, I am of the (biased) opinion that openLilyLib is a
> powerful and useful extension infrastructure for LilyPond. There are a
> number of versatile and extend
1 - 100 of 393 matches
Mail list logo
