Am Montag, den 24.08.2020, 09:06 +0200 schrieb Werner LEMBERG:
> > I've reordered and rebased my code, and it is now up to date with
> > the current master. I've just published the new branch to GitLab
> as
> > dev/lamb/GSoC-2020-final if you'd like to give it a look. It's
> only
> > nine commits
Am Mittwoch, den 19.08.2020, 09:24 +0200 schrieb Werner LEMBERG:
> >> git remote update
> >> git push --mirror g...@github.com:lilypond/lilypond.git
> >
> > Definitely add --prune to "git remote update" to remove branches
> > that ceased to exist on the remote.
>
> OK, done.
>
> > In general
Am Dienstag, den 18.08.2020, 02:44 +0200 schrieb Urs Liska:
>
> Am 18. August 2020 01:01:20 MESZ schrieb Andrew Bernard <
> andrew.bern...@gmail.com>:
> > Please pardon me for asking this once again... but where does one
> > find
> > the set of changes jus
Am 18. August 2020 01:01:20 MESZ schrieb Andrew Bernard
:
>Please pardon me for asking this once again... but where does one find
>the set of changes just for this release, not that long accumulated
>list
>in the documentation? I have forgotten where this info is.
I don't know whether this i
Hi Owen,
it's always a pleasure seeing your project evolve and proceed. I'd like
to throw in a comment, although I'm rather sure it isn't actually
needed.
Am Freitag, den 07.08.2020, 21:49 -0700 schrieb Owen Lamb:
> Hi all!
>
> ...
>
> --turned out to be a major point of difference between
> Lil
Am 1. August 2020 23:31:32 MESZ schrieb Jean Abou Samra :
>Hi everyone,
>
>Le 01/08/2020 à 18:19, Urs Liska a écrit :
>> Am 1. August 2020 16:12:24 MESZ schrieb Werner LEMBERG :
>>>>> Another issue: Maybe it makes sense if you try to rebase your
>>>&g
Am 1. August 2020 16:12:24 MESZ schrieb Werner LEMBERG :
>>> Another issue: Maybe it makes sense if you try to rebase your
>>> branch from time to time.
>>
>> Really rebase?
>
>Yes, I favour rebasing over merging since the former causes a
>`prettier' git commit tree.
>
>> This would be a case w
Am 1. August 2020 06:59:16 MESZ schrieb Werner LEMBERG :
>
>> In the meantime, I've gotten Bravura glyphs to appear on the page!
>
>Congrats!
>
>A question to commit d092b23276059c77e33cab9428b9a9753b5cd27a: Why do
>you change from the (IMHO preferable) `-` to `_` in the file name? I
>consider
Am Freitag, den 10.07.2020, 10:34 +0200 schrieb Jean-Julien Fleck:
> Hello Urs,
>
> Le ven. 10 juil. 2020 à 09:03, Urs Liska a
> écrit :
> >
> > But I'd like to repeat that the fonts created by Abraham (including
> >
> > Gonville) are at least pa
Am Donnerstag, den 09.07.2020, 21:40 +0200 schrieb Paolo Prete:
> On Thu, Jul 9, 2020 at 8:35 PM Jean Abou Samra
> wrote:
>
> > Le 08/07/2020 à 15:31, Paolo Prete a écrit :
> >
> >
> >
> > On Wed, Jul 8, 2020 at 12:13 PM Jean Abou Samra > >
> > wrote:
> >
> > > I would like to emphasize that
Am Samstag, den 04.07.2020, 10:06 -0500 schrieb Karlin High:
> On 7/4/2020 5:55 AM, Paolo Prete wrote:
> > Just leave Feta as a native font and insert a dummy
> > wrapper for Gonville in the ./configure. This does not require any
> > development, nor uniformity in the coding standard and can be
> >
Am Dienstag, den 16.06.2020, 09:16 +0200 schrieb Han-Wen Nienhuys:
> Isn't Smufl a standard proposed by the Dorico folks?
Yes and no. Daniel Spreadbury spearheaded the effort while Dorico was
developed. But it was originally conceived as an open standard.
> We could try to
>
> agree on a mechan
Am Donnerstag, den 04.06.2020, 13:36 +0200 schrieb Jean Abou Samra:
> Hi,
> Le 04/06/2020 à 08:31, James Lowe a écrit :
> > On 03/06/2020 21:25, Karlin High wrote:
> > > On 6/3/2020 3:14 PM, Jean Abou Samra wrote:
> > > > There is a discussion at
> > > > https://gitlab.com/lilypond/lilypond/-/issu
Hi Owen!
Am 27. Mai 2020 22:58:19 MESZ schrieb Owen Lamb :
>Hi all!
>
>I pushed the new dev/lamb/GSoC-2020 branch to origin yesterday, and it
>appears to be visible on GitLab. I haven't committed anything new yet,
>but
>I will soon. I'll push any commits I make at the end of each work day.
>
>I pl
Am Montag, den 25.05.2020, 20:30 +0200 schrieb Jonas Hahnfeld:
> Am Samstag, den 23.05.2020, 16:38 +0200 schrieb Urs Liska:
> > Am 23. Mai 2020 15:01:11 MESZ schrieb Werner LEMBERG :
> > > > I can grant you access to the repository later today if needed.
> > &g
Am 23. Mai 2020 15:01:11 MESZ schrieb Werner LEMBERG :
>
>> I can grant you access to the repository later today if needed.
>> However I'd first like to understand (probably from Werner) what
>> makes a branch in the upstream repository more "preserving" than a
>> public clone. Being distribute
Am 21. Mai 2020 19:21:27 MESZ schrieb Owen Lamb :
>>
>> To preserve your code within LilyPond it probably makes sense if you
>put
>> your code into a private (but public) branch of the upstream lilypond
>> repository (i.e., not a gitlab clone of it), for example
>> 'dev/lamb/GSoC-2020'.
>>
>
>I'
Am Montag, den 18.05.2020, 11:15 +0100 schrieb Kevin Barry:
> On Mon, May 18, 2020 at 10:48:55AM +0100, James Lowe wrote:
> > but how do I know? That is the nub of what I am asking. If a patch
> > is 'new'
> > how do I know that an automated make doc is 'in progress, has
> > completed with
> > erro
Am Sonntag, den 17.05.2020, 10:01 +0200 schrieb Han-Wen Nienhuys:
> On Sun, May 17, 2020 at 9:55 AM Urs Liska
> wrote:
> > Hello all,
> >
> > although I have admittedly been pretty much silent about all this I
> > would like to ask about getting access to the Lily
Hello all,
although I have admittedly been pretty much silent about all this I
would like to ask about getting access to the LilyPond repository in
the new place as well. My user name there is urs.liska.
One thing I noted while setting up my account is that we don't have a
README.md in the root d
Am Mittwoch, den 13.05.2020, 22:33 -0400 schrieb Dan Eble:
> On May 13, 2020, at 17:13, David Kastrup wrote:
> > > > At the current point of time, our pipeline does not tend to be
> > > > all that
> > > > full I think. We are not at Linux kernel levels of
> > > > participation...
> > >
> > > No,
Am Montag, den 11.05.2020, 11:52 +0200 schrieb Jonas Hahnfeld:
> Am Montag, den 11.05.2020, 11:39 +0200 schrieb Werner LEMBERG:
> > > I granted everybody access to the group
> > > https://gitlab.com/lilypond who
> > > sent requests so far.
> >
> > Please give me access too; my username on GitLab
Am 11. April 2020 15:33:06 MESZ schrieb David Kastrup :
>Jonas Hahnfeld writes:
>
>> Hi all,
>>
>> following removal of dev/translation-* branches, I took a closer look
>> at stale branches. I think it would make sense to keep unscoped
>> branches (outside of dev/user/) to a minimum. This shoul
Hi all,
an hour ago this year's GSoC student application deadline has been
completed, and it seems I'm currently the only registered mentor having
access to that.
Of course we can't discuss application(s) on public lists. So please
reply to me privately so I can share the application(s) with you
Am 26. März 2020 17:46:07 MEZ schrieb Carl Sorensen :
>
>
>On 3/26/20, 10:12 AM, "lilypond-devel on behalf of David Kastrup"
>d...@gnu.org> wrote:
>
>
> So it's time to roll out 2.21.0 and I think the build instructions are
> ok-ish for that. We don't clarify the relations/recommendation
Am 26. März 2020 17:11:36 MEZ schrieb David Kastrup :
>
>So it's time to roll out 2.21.0 and I think the build instructions are
>ok-ish for that. We don't clarify the relations/recommendations for
>Guile-1.8/2.x but that relation/recommendation is currently in flux and
>this is an unstable rele
Hello Brahim,
Am Montag, den 16.03.2020, 10:31 + schrieb brahim.pro via
Discussions on LilyPond development:
> Hello,
>
> I would like to use lilypond parser in my own application.
> I can't find any API or external library to do that.
There is no such thing.
> What is the correct approach
Am Donnerstag, den 27.02.2020, 08:57 -0300 schrieb Leandro Doctors:
> On Wed, 26 Feb 2020 at 18:56, Urs Liska
> wrote:
> > I'd like to stress that the GSoC page lists
> > project *ideas*, and if you're specifically interested in Scheme
> > stuff
> > y
Am Mittwoch, den 26.02.2020, 15:46 -0600 schrieb Karlin High:
> On 2/26/2020 3:28 PM, Leandro Doctors wrote:
> > Could you please point me in the right direction?
>
> Thanks for your interest! In the past, Urs Liska has been leading
> GSOC
> efforts. He's indic
Am Donnerstag, den 13.02.2020, 18:48 +0100 schrieb Jean-Charles
Malahieude:
> Le 13/02/2020 à 15:10, Han-Wen Nienhuys a écrit :
> > FYI, lilypond.org is now serving on HTTPS
> >
> > See here https://codereview.appspot.com/559470043/ for background.
> >
>
> This should be applied on stable/2.20 a
Just to let you know: GNU has been accepted as a GSoC mentoring
organization.
a)
This means that now people may visit
https://lilypond.org/google-summer-of-code.html and look at our GSoC
project ideas. So if anythingg could be added (or fixed or removed)
there now would be the (latest) time to do
Am Donnerstag, den 20.02.2020, 17:12 +0100 schrieb David Kastrup:
> David Kastrup writes:
>
> > Graham Percival writes:
> >
> > > On Sun, Jan 22, 2012 at 11:49:06AM +0100, David Kastrup wrote:
> > > > Anybody actually using the "music-cause"? Inside of LilyPond,
> > > > the only
> > > > appear
Am Montag, den 17.02.2020, 13:25 +0100 schrieb David Kastrup:
> Ok, I think 2.20 is basically done and we should push it out by the
> end
> of this week.
This is really great news!
I'm somewhat undecided whether it is a cause for celebration or not to
finally release a "stable" version after six
I just told them to copy last year's proposal, which basically links to *our*
GSoC page.
Urs
Am 12. Februar 2020 20:03:49 MEZ schrieb David Kastrup :
>
>Someone with a good idea?
>
> Start of forwarded message
>From: jema...@gnu.org (Jose E. Marchesi)
>To
Am 8. Februar 2020 19:23:34 MEZ schrieb Karlin High :
>On 2/8/2020 11:24 AM, Phil Holmes wrote:
>> I remain strongly opposed to a CoC.
>
>Clearly noted; thanks for responding. I have nothing further to say on
>this topic just now; it's pretty much all been covered in prior
>messages.
>
>I'm sor
Am Samstag, den 08.02.2020, 17:52 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > Am Samstag, den 08.02.2020, 17:31 +0100 schrieb David Kastrup:
> > > Thomas Morley writes:
> > >
> > > > P.S. that 'make test-baseline' failed, I'
Am Samstag, den 08.02.2020, 17:31 +0100 schrieb David Kastrup:
> Thomas Morley writes:
>
> > P.S. that 'make test-baseline' failed, I'll need to investigate
> > after
> > sending this.
> >
> >
>
> input/regression/display-lily-tests.ly:230:1: fatal error: Test
> unequal: BUG.
> in = \applyOut
Am 7. Februar 2020 09:48:30 MEZ schrieb Kevin Barry :
>> (CC to Kevin Barry, who mentioned GitLab experience in a separate
>> thread. My info here is more based on research than experience, so
>> please call out any misunderstandings I have.)
>
>Thank you for the CC. I have read through the mess
Am Mittwoch, den 05.02.2020, 22:26 -0500 schrieb Kieren MacMillan:
> Hi Graham,
>
> > Oh, that would definitely be a good idea!
>
> Okay, then! I’ll start with your suggestion to [paraphrasing:]
> "summarize the jobs described in the CG", and prepare a skeleton
> document where each entry is like
Am Mittwoch, den 05.02.2020, 21:21 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > Am 5. Februar 2020 20:08:28 MEZ schrieb
> > nine.fierce.ball...@gmail.com:
> > > On 2020/02/05 18:17:25, c_sorensen wrote:
> > > > I recognize that Mike Solomon has
Am 5. Februar 2020 20:08:28 MEZ schrieb nine.fierce.ball...@gmail.com:
>On 2020/02/05 18:17:25, c_sorensen wrote:
>> I recognize that Mike Solomon has a different opinion. I mean no
>disrespect to
>> Mike, Janek, Han-Wen, or any other member of the LilyPond team. I
>highly value
>> the team sp
Hi all,
I wanted to get a better understanding from my impression of the
significant increase in traffic on lilypond-devel.
For this I did some statistics on James' "PATCHES - Countdown"
messages. Since patches are counted multiple times while flowing
through the process I think the only relevant
Am Freitag, den 31.01.2020, 18:38 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > Am Mittwoch, den 29.01.2020, 07:01 -0800 schrieb d...@gnu.org:
> > > On 2020/01/29 12:20:10, mail5 wrote:
> > > > Unfortunately I haven't set up a build system
Am Donnerstag, den 30.01.2020, 09:50 +0100 schrieb Han-Wen Nienhuys:
> On Tue, Jan 28, 2020 at 2:48 PM David Kastrup wrote:
>
> > > I think we should aim to avoid textual inclusion as a mechanism
> > > that
> > > powers packaging.
> >
> > At the implementation side, "textual inclusion" will be w
Am Mittwoch, den 29.01.2020, 07:01 -0800 schrieb d...@gnu.org:
> On 2020/01/29 12:20:10, mail5 wrote:
> > Unfortunately I haven't set up a build system on my new computer
> > yet,
> so this
> > patch is not tested locally at all, so I'm humbly waiting for the
> automated
> > tests to succeed or fai
One final question before I start working on some package code
proposal:
All the basic Scheme files are loaded in lily.scm with
(for-each ly:load init-scheme-files)
What does this do internally? I.e. how is the visibility handled of
definitions/bindings from names in files loaded with ly:load
Am 28. Januar 2020 14:48:54 MEZ schrieb David Kastrup :
>Han-Wen Nienhuys writes:
>
>> On Mon, Jan 27, 2020 at 11:39 PM Urs Liska
>wrote:
>>>
>>> I didn't have time to really think about much (about LilyPond) the
>past
>>> week, j
Am Dienstag, den 28.01.2020, 09:26 +0100 schrieb Han-Wen Nienhuys:
> On Mon, Jan 27, 2020 at 11:39 PM Urs Liska
> wrote:
> > I didn't have time to really think about much (about LilyPond) the
> > past
> > week, just enjoyed seeing so much constructive discussion.
>
Am Dienstag, den 28.01.2020, 00:34 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > I didn't have time to really think about much (about LilyPond) the
> > past
> > week, just enjoyed seeing so much constructive discussion.
> >
> > I think th
I didn't have time to really think about much (about LilyPond) the past
week, just enjoyed seeing so much constructive discussion.
I think the first thing I'd like to go for with the package/extension
mechanism is storing and handling (package) options.
There are three use cases which are differe
Am 25. Januar 2020 08:56:44 MEZ schrieb Werner LEMBERG :
>
>> What is "french beaming" supposed to do/be?
>
>No stems within the beam.
Ah, yes. Sorry for forgetting that...
>
>
>Werner
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Am 25. Januar 2020 08:36:08 MEZ schrieb Han-Wen Nienhuys :
>Looks like a bug.
What is "french beaming" supposed to do/be?
>
>On Sat, Jan 25, 2020 at 8:12 AM Werner LEMBERG wrote:
>>
>>
>> Before adding it to the bug tracker I want to check this group's
>> knowledge whether there is a reason t
Am Freitag, den 24.01.2020, 11:41 +0100 schrieb Han-Wen Nienhuys:
> On Fri, Jan 24, 2020 at 11:28 AM David Kastrup wrote:
>
> > Han-Wen Nienhuys writes:
> >
> > > Thanks for keeping track of this.
> > >
> > > Can you confirm my countdown patches will get pushed without any
> > > of my
> > > in
Am Mittwoch, den 22.01.2020, 11:43 +0100 schrieb Urs Liska:
> Am Mittwoch, den 22.01.2020, 11:06 +0100 schrieb David Kastrup:
> > Urs Liska writes:
> >
> > > Am Dienstag, den 21.01.2020, 11:19 +0100 schrieb Urs Liska:
> > > > > Ok. One thing to th
Am Mittwoch, den 22.01.2020, 20:28 + schrieb Carl Sorensen:
>
> On 1/22/20, 1:21 PM, "lilypond-devel on behalf of David Kastrup" <
> lilypond-devel-bounces+c_sorensen=byu@gnu.org on behalf of
> d...@gnu.org> wrote:
>
> Han-Wen Nienhuys writes:
>
> > On Wed, Jan 22, 2020 at
Am Mittwoch, den 22.01.2020, 11:06 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > Am Dienstag, den 21.01.2020, 11:19 +0100 schrieb Urs Liska:
> > > > Ok. One thing to think about is that we want package files to
> > > > be
> > > > cont
Am Dienstag, den 21.01.2020, 11:19 +0100 schrieb Urs Liska:
> > Ok. One thing to think about is that we want package files to be
> > contributed by "ordinary" users. But something like
> >
> > \exportSymbols transposeSequence,instrumentGroup,scratchMyBack
&g
We have discussed options already on a conceptual level as "package
options", but technically it should be dealt with separately.
Options are not functionally required for the package loading to work,
but they are an integral part of the functionality, and I have found
that their availability has
Am Dienstag, den 21.01.2020, 03:56 -0800 schrieb lemzwerg--- via
Discussions on LilyPond development:
> Very nice, thanks!
>
> https://codereview.appspot.com/571380043/
>
I've only looked at it cursorily, but I think this is really a step in
the right direction (even if it may feel like the drop
Am Montag, den 20.01.2020, 23:45 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > OK. The *current* behaviour of oll-core is:
> >
> > * loaded packages and modules (let's for now keep the existing
> > names)
> > are accounted for in an alist.
Am Montag, den 20.01.2020, 14:14 +0100 schrieb David Kastrup:
> Urs Liska writes:
>
> > Am Montag, den 20.01.2020, 10:27 +0100 schrieb Urs Liska:
> > > * A core extension library shipping with LilyPond will be
> > > initiated.
> > > Extensions that a
Am Montag, den 20.01.2020, 16:53 +0100 schrieb David Kastrup:
> David Kastrup writes:
>
> > Werner LEMBERG writes:
> >
> > > > > Han-Wen has recently pushed a bunch of changes directly to
> > > > > Rietveld, most of them quite uncontroversial. I assume that
> > > > > this
> > > > > is as good
Am Montag, den 20.01.2020, 10:27 +0100 schrieb Urs Liska:
> * A core extension library shipping with LilyPond will be initiated.
> Extensions that are considered core functionality (prime
> candidates:
> edition-engraver, stylesheets) will eventually be moved here from
>
I'll have a look ASAP:
Urs
>
> On Mon, Jan 20, 2020 at 9:22 AM Urs Liska
> wrote:
> > Hi all,
> >
> > how/where is the file searchign with LilyPond's search path is
> > implemented?
> >
> > If I write
> > \include "a/relati
Hi,
one of the results of yesterday's developer meeting in Salzburg
[someone™ should provide a more concise summary than the notes in the
GoogleDoc] was that I should go forward "integrating openLilyLib" as
LilyPond's official extension mechanism.
I spent my travel back home reading through the c
Hi all,
how/where is the file searchign with LilyPond's search path is
implemented?
If I write
\include "a/relative/path"
the given path is searched for relative to all search paths known to
LilyPond.
Is there a way to do the same in Scheme, say
(file-visible-to-lilypond "a/relative/path")
.
>
>contributions in GitHub are usually stored on a branch + fork owned by
>the contributor, e.g.
>
> https://github.com/mikesol/lilypond/
>
>branch code_of_conduct.
I think that needs clarification.
Forks are "usually" used by people without push access to a repository. People
*with* push a
Am Sonntag, den 19.01.2020, 20:31 + schrieb Erlend Aasland:
> True. But, there are GitHub alternatives that are free, for example
> Gitea.
Yes, but self-hosting a Git repository software (well, I have a Gitea
instance on my server) is an involved thing, and I don't think it's
reasonable to exp
Am Sonntag, den 19.01.2020, 07:20 +0100 schrieb Werner LEMBERG:
> > While that may be true, there are already GNU projects using GitHub
> > as their host, for example gnucash and gnuradio.
>
> Gnucash uses github as a mirror only, see
>
> https://wiki.gnucash.org/wiki/Git#code.gnucash.org
>
>
Am Montag, den 13.01.2020, 15:42 -0500 schrieb Kieren MacMillan:
> Hello future Salzburg-ers!
>
> Knowing the way my life works, and the fact that I’ll be in Salzburg
> for four days without the normal distractions (family, etc.), and at
> hand will be a rather wonderful collection of brains and f
Hi Kieren,
Am Samstag, den 11.01.2020, 11:03 -0500 schrieb Kieren MacMillan:
> Hello colleagues!
>
> I just had a wonderful video-chat with Jan-Peter, as part of the
> preparations for my session “The Edition-Engraver: The benefits and
> limitations of tweaking LilyPond scores” at next week’s
> [
Am 7. Januar 2020 23:53:42 MEZ schrieb Andrew Bernard
:
>Hi Malte,
>
>\shapeII is a function I use heavily - heavily - in all my work. It's
>indispensable for me at least. I'm very familiar with OpenLilyLib, and
>contribute a bit to it, so it's not an issue for me, but that's a
>function that r
4. Januar 2020 12:34, "Malte Meyn" schrieb:
> Am 04.01.20 um 12:29 schrieb Malte Meyn:
>
>> But that brings me to another question: Shouldn’t we add the \dynamic >
>> command from openlilylib to
>> vanilla LilyPond? This would allow users to > have “p dolce”, “più f” and
>> ‘exotic’ dynamics l
Am 16.12.19 um 10:18 schrieb Urs Liska:
* For integration in LilyPond the functionality should be wrapped into
a single file that can be included. Including the file should
automatically activate the functionality.
Maybe there should be a second includable file that does *not
Any LilyPond dev who does have a Facebook account might have a look at
this interesting, although somewhat sad, discussion. I think it gives a
clear picture of how our current state of development is perceived by users:
https://www.facebook.com/groups/gnulilypond/permalink/10157762793383529/
U
Hi Jan-Peter,
that sounds like a very nice idea.
However, I'm so involved in the conference already (along with my other
duties which are quite overwhelming right now) that I can't commit to
that beyond maybe occasional commenting or helping out with some
lyluatex syntax/options.
From what
Am 15. November 2019 14:35:26 MEZ schrieb David Nalesnik
:
>On Fri, Nov 15, 2019 at 12:33 AM Urs Liska
>wrote:
>>
>> Hi David,
>>
>> I feel responsible for this because I know where this is coming from
>;-)
>
>Hah! :) (Seriously, though, this is som
Hi David,
I feel responsible for this because I know where this is coming from ;-)
You can send me the patch. However, it's a long time since I uploaded
anything, so I'm not sure my set-up still works. But I'll try.
Best
Urs
Am 15.11.19 um 04:10 schrieb David Nalesnik:
Hi all,
I have a pa
Am 12. November 2019 10:50:45 MEZ schrieb David Kastrup :
>Werner LEMBERG writes:
>
>>>> This package is written by Urs Liska , who is
>>>> quite busy these days. In case you have experience with Python 2
>>>> to 3 conversion, please help produce
27. September 2019 08:55, "Urs Liska" schrieb:
> Hi Werner,
>
> thanks for working on this.
>
> I have the impression it would be nice to add at least one example with an
> alternative notation
> font to the example page. Here is the list of freely availa
Hi Werner,
thanks for working on this.
I have the impression it would be nice to add at least one example with an
alternative notation font to the example page. Here is the list of freely
available fonts:
https://github.com/openlilylib-resources/lilypond-notation-fonts/tree/master/fonts
(note
Hi Martin,
23. September 2019 11:17, "Martin Tarenskeen" schrieb:
> Hi,
>
> This has been discussed here before but https://pythonclock.org made me
> wonder in which direction LilyPond and Frescobaldi are currently going.
Well, if you're wondering about the direction then you might just read
Am 21. September 2019 19:09:55 MESZ schrieb David Kastrup :
>Werner LEMBERG writes:
>
>> Here's an updated version of the Stockhausen example, with a lot of
>> added comments to the source code.
>>
>> I've also attached an image of rendering the old code (as present in
>> the git) with a lilypon
Am 21. September 2019 04:09:36 MESZ schrieb Andrew Bernard
:
>So let me get this straight.
>
>It's not the case that GUB is completely broken. We can still build
>releases.
>
>DK is working steadily to cherry pick items for 2.20.
>
>Python 2 to Python 3 is a major issue.
>
>So, I offered to do
Am 20. September 2019 02:23:58 MESZ schrieb Carl Sorensen :
>We are stuck for release because GUB is not working properly. Until we
>get GUB to work properly, we cannot make a release.
>
>As far as I know now, the answer is in fact indefinite.
But is that the actual roadblock for the *2.20* rel
Hi Werner,
thank you for that!
I can't comment on it because I don't know much about Schenker graphs. But I
could right away use it ;-)
https://github.com/frescobaldi/frescobaldi/pull/1173#issuecomment-531884243
(actually this was something I had been hoping for).
Best
Urs
16. September 2019
Hi Kim,
thank you for the suggestion.
4. August 2019 16:14, "hs kim" schrieb:
> Hi.
> I was making "la campanella". There was many subdivide beams but it was so
> confused that I can't make it anymore. That's why I decided to change the
> way subdivide beams are written.
>
> In the stable bran
30. Juli 2019 11:16, "David Kastrup" schrieb:
> "Urs Liska" writes:
>
>> I'm not sure if this is actually a *development* request or if it
>> could also be solved at the "user" level.
>>
>> As Werner showed in https://gi
I'm not sure if this is actually a *development* request or if it could also be
solved at the "user" level.
As Werner showed in https://github.com/jperon/lyluatex/issues/268
(https://github.com/jperon/lyluatex/issues/268) there is an issue with the
output of scores compiled with `lilypond-book-
Thank you for doing so.
The thing is (as buried in a comment somewhere), these regular reminders served
as an incentive for me not to forget that I wanted to push this only after
documenting the new feature...
___
lilypond-devel mailing list
lilypond-
Am 04.06.19 um 10:53 schrieb Urs Liska:
Am 04.06.19 um 00:13 schrieb thomasmorle...@gmail.com:
https://codereview.appspot.com/570690043/diff/564820043/scm/color.scm
File scm/color.scm (right):
https://codereview.appspot.com/570690043/diff/564820043/scm/color.scm#newcode678
scm/color.scm
Am 04.06.19 um 00:13 schrieb thomasmorle...@gmail.com:
https://codereview.appspot.com/570690043/diff/564820043/scm/color.scm
File scm/color.scm (right):
https://codereview.appspot.com/570690043/diff/564820043/scm/color.scm#newcode678
scm/color.scm:678: (define css-color-list
Is there anythin
Am 18.05.19 um 05:53 schrieb Carl Sorensen:
1.8
It's actually 1.8.8 IIRC
Urs
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am 06.04.19 um 01:49 schrieb Kieren MacMillan:
Hi Werner,
Would this be of interest for LilyPond?
https://developers.google.com/season-of-docs/docs/project-ideas
It would be *very* valuable for OpenLilyLib… =)
Indeed, but I don't think this program is suitable for that ...
If I've underst
Hi Tsz Kiu,
Am 03.04.19 um 13:48 schrieb Tsz Kiu Pang:
Hi Urs,
Whether or not I'll be suitable to participate in GSoC, I am keen to
dive into openlilylib.
That would be great!
On Thu, 21 Mar 2019 at 17:58, Urs Liska <mailto:li...@openlilylib.org>> wrote:
What you
This is directed at the other devs, to (please) join the conversation
Am 01.04.19 um 08:30 schrieb Tsz Kiu Pang:
I just have some concerns.
Sorry I might have overestimated myself in the past week, but I
realised I might not be able to commit for 30+ hours per week
during May s
Hi Tzk Kiu,
Am 21.03.19 um 13:06 schrieb Tsz Kiu Pang:
Hi Urs,
Thank you for your reply, and thank you so much for asking about my name.
On Thu, 21 Mar 2019 at 17:58, Urs Liska <mailto:li...@openlilylib.org>> wrote:
Hi Tsz Kiu Pang (which of these names would you like to be c
Hi Tsz Kiu Pang (which of these names would you like to be called, or
should I use all of them like I did?)
Am 21.03.19 um 06:58 schrieb Tsz Kiu Pang:
Hi all,
I am writing to express my interest in working on LilyPond as part of GNU
in the Google Summer of Code.
I was just looking at the proj
Am 16. März 2019 20:20:15 MEZ schrieb Valentin Villenave
:
>On 3/16/19, Valentin Petzel wrote:
>> Currently the anchor points are set both over or both under the
>starting /
>> ending note, depending on the slur’s direction. For the S-shape we
>would
>> need
>> the control points to differ in d
Hi Daniel,
Am 27.02.19 um 15:00 schrieb Daniel Benjamin Miller:
Hi all:
I'm an undergraduate student at McGill University. As I've personally
wanted to tweak LilyPond to improve the stylistic output of my scores,
I was hoping to do some work on LilyPond this summer, perhaps through
GNU's inv
1 - 100 of 754 matches
Mail list logo
