Re: [RFC] switch to GitLab / gitlab.com

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

Re: Add Code of Conduct

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

Re: Add Code of Conduct

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'

Re: Add Code of Conduct [Another RFC or not now?]

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

Re: [Jose E. Marchesi] [gnu-prog-discuss] [VERY URGENT] GNU ideas for GSOC 2020

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

Re: 2.20 and 2.21 release plans

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

Re: music-cause

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

GSoC

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

Re: lilypond.org now serving HTTPS

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

Re: [GSOC 2020] Discussing GNU Lilypond project ideas?

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

Re: [GSOC 2020] Discussing GNU Lilypond project ideas?

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

Re: Lilypond API

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

Re: 2.21.0 and announcements

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

Re: 2.21.0 and announcements

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

GSoC applications

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

Re: stale git branches

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

Re: repository at GitLab

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

Re: Obstacles for using GitLab CI

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,

README.md (was: migrating to GitLab)

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

Re: README.md (was: migrating to GitLab)

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

Re: [RFC] Enabling GitLab CI

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

Re: LilyPond GSoC logistics

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'

Re: Access to push new branch to origin

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

Re: Access to push new branch to origin

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

Re: GSoC 2020 update

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

Re: Remove lily-git?

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

Re: GSoC 2020 update, June 15

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

Re: Accidentals' font

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 > >

Re: Accidentals' font

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

Re: Accidentals' font

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

Re: GSoC-2020 update: Jul 31

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

Re: GSoC-2020 update: Jul 31

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

Re: GSoC-2020 update: Jul 31

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

Re: GSoC 2020 update: Aug 7

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

Re: LilyPond 2.21.5 release

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

Re: LilyPond 2.21.5 release

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

Re: maintaining lilypond git repository on github

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

Re: GSoC 2020 update: (hopefully) final commits made; testing time

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

Re: Scheme in LilyPond

Am 01.06.2017 um 17:41 schrieb Paul: > On 06/01/2017 11:03 AM, Charles Winston wrote: > >> And I get an error saying that make-note-ev is an unbound variable. I >> thought that we could call Scheme procedures from the source in >> lilypond files. What am I missing here? > > I'll just add that gen

Re: Some questions related to score video generation

Hi Knut, very interesting project (which should be included in my plan for an additional "interesting uses" page on lilypond.org). Some comments (but explicitly without any warranty): Am 07.07.2017 um 09:55 schrieb Knut Petersen: > Hi everybody! > > I extended my video generation script to allow

Re: Some questions related to score video generation

Am 07.07.2017 um 15:00 schrieb Knut Petersen: > Am 07.07.2017 um 12:04 schrieb Knut Petersen: > > There is a new version of the demonstration video online: I > Fyrreskoven. > Coloring of stems / flags /dots works now. Great! I'll have to see whom I c

Fwd: Possible opportunity for GNU contributions by FSF intern this fall

Ursprüngliche Nachricht Von: Andrew Engelbrecht Gesendet: 5. September 2017 19:40:38 MESZ An: summer-of-c...@gnu.org Betreff: Possible opportunity for GNU contributions by FSF intern this fall Hello GNU maintainers, The FSF tech team may take on a full or part time intern th

LilyPond in Debian

Hi all, I'm investigating Debian again, looking for a new system for me. So far I've done a pretty minimal installation of Debian Buster (current "Testing"), looked for LilyPond and Guile - and was somewhat surprised. Last time I looked I found that the "lilypond" package had been removed from De

Re: LilyPond in Debian

Am 11.09.2017 um 10:41 schrieb David Kastrup: > Urs Liska writes: > >> Hi all, >> >> I'm investigating Debian again, looking for a new system for me. So far >> I've done a pretty minimal installation of Debian Buster (current >> "Testing&

Re: LilyPond in Debian

Am 11.09.2017 um 11:23 schrieb David Kastrup: > Urs Liska writes: > >> Yes, indeed better than nothing (sudo apt install lilypond => "package >> lilypond has no release candidate"). >> OTOH it may take some pressure off the need for a "proper"

Re: LilyPond in Debian

Am 11.09.2017 um 12:10 schrieb Federico Bruni: > Il giorno lun 11 set 2017 alle 10:53, Urs Liska > ha scritto: >> could I install Guile 1.8 from sid and use that for setting up my >> LilyPond environment? I really don't want to use an extra virtual >> machine just f

Re: LilyPond in Debian

Am 11.09.2017 um 14:47 schrieb David Kastrup: > Urs Liska writes: > >> Am 11.09.2017 um 11:23 schrieb David Kastrup: >>> Urs Liska writes: >>> >>>> Yes, indeed better than nothing (sudo apt install lilypond => "package >>>> l

Re: LilyPond in Debian

Hi Knut, thank you for the script. Am 12.09.2017 um 09:34 schrieb Knut Petersen: > >> Hm, will I be able to get a system where I can build LilyPond again? > > Urs, building guile 1.8 is a pretty trivial and fast process. Just do > it and don't care about debian OK, I see how you build Guile dir

Re: LilyPond in Debian

Am 12.09.2017 um 14:09 schrieb Knut Petersen: > Am 12.09.2017 um 11:38 schrieb Urs Liska: >> Hi Knut, >> >> thank you for the script. >> >> >> Am 12.09.2017 um 09:34 schrieb Knut Petersen: >>>> Hm, will I be able to get a system where I can bui

Re: LilyPond in Debian

Am 12.09.2017 um 18:39 schrieb Knut Petersen: > Am 12.09.2017 um 16:46 schrieb Urs Liska: >> >>>> And more, can't I build Guile once, into some other directory and >>>> rather >>>> than rebuilding it each time place a symlink into the LilyPo

Re: LilyPond in Debian

Am 13.09.2017 um 10:33 schrieb Knut Petersen: > Am 12.09.2017 um 23:28 schrieb Urs Liska: >>> I think deleting every of the two occurrences of the string "64" in >>> the build script has a good chance to cure the problem. >> Thank you, this actually worked.

Re: LilyPond in Debian

Am 13.09.2017 um 11:21 schrieb Knut Petersen: > >> This is not the root of the issue, since: >> >> $ uname -r >> 4.9.0-3-amd64 > > But what's the output of "uname*-m*"? x86_64 > > Knut > ___ lilypond-devel mailing list lilypond-devel@gnu.org h

Terminology of baseMoment, beats, groups

Hi all, I'm writing an assessment how the beaming-pattern code could be redone properly, which is pretty much necessary. Apart from some minor problems at the surface at least the concept of (subdivide the) beaming of tuplets it completely messed up. In fact, beam subdivision is simply unusab

Re: Terminology of baseMoment, beats, groups

Am 11.11.2017 um 11:42 schrieb David Kastrup: Urs Liska writes: So, now the first question ... The terminology of baseMoment, beats and groups is inconsistent between the NR (http://lilypond.org/doc/v2.19/Documentation/notation/beams#setting-automatic-beam-behavior) and the code. The

Re: Terminology of baseMoment, beats, groups

Am 11.11.2017 um 12:30 schrieb David Kastrup: I find "grouping" without "beat" fine. I could have been responsible for the terminology in the code (pretty sure I wasn't, but it matches the terminology I use quite better). Now I have certainly not gotten an English music education, so can some

Re: Terminology of baseMoment, beats, groups

Am 11.11.2017 um 12:52 schrieb Urs Liska: "Beat" also refers to what a conductor would do. the 3+3+2 from my example would be given as three "beats" by the conductor. Maybe your perception of "beat" as necessarily regular comes from the fact that in German

Re: Terminology of baseMoment, beats, groups

Am 11.11.2017 um 13:15 schrieb David Kastrup: Urs Liska writes: Am 11.11.2017 um 12:30 schrieb David Kastrup: I find "grouping" without "beat" fine. I could have been responsible for the terminology in the code (pretty sure I wasn't, but it matches the termi

Re: Terminology of baseMoment, beats, groups

Am 11.11.2017 um 13:25 schrieb Simon Albrecht: On 11.11.2017 12:30, David Kastrup wrote: I have a hard time seeing a "beat" as something that can have different lengths. Musical notation isn’t well-defined in a mathematical or programming sense, so there are no such strict rules as all beat

Re: Terminology of baseMoment, beats, groups

Am 11.11.2017 um 21:23 schrieb David Kastrup: Urs Liska writes: Am 11.11.2017 um 15:30 schrieb Carl Sorensen: When I look at http://openmusictheory.com/meter.html , the thing that we call a beat in the c++ code is what openmusictheory calls a pulse. And what we call a beat group is what

Re: Terminology of baseMoment, beats, groups

Am 11.11.2017 um 15:07 schrieb Hans Åberg: On 11 Nov 2017, at 12:52, Urs Liska wrote: Am 11.11.2017 um 12:30 schrieb David Kastrup: I find "grouping" without "beat" fine. I could have been responsible for the terminology in the code (pretty sure I wasn't, but i

Re: New Status "Shelved" in LilyPond Bug Tracker

Am 11. Dezember 2017 17:50:01 MEZ schrieb Trevor : > >Devs and Bug Trackers > >I have implemented a new Status field in the Issues Tracker at >SourceForge: Status:Shelved, with the meaning: > >"Probably desirable, but impractical to implement at present due to >lack >of resources". > >There is

Re: Issue #5246: Make empty scores abort engraving process (issue 332470043 by beauleetien...@gmail.com)

Am 22. Dezember 2017 15:42:39 MEZ schrieb David Kastrup : >Dan Eble writes: > >> On Dec 21, 2017, at 23:06, beauleetien...@gmail.com wrote: >>> >>> @@ -110,8 +110,7 @@ LY_DEFINE (ly_interpret_music_expression, >"ly:interpret-music-expression", >>> >>> if (!iter->ok ()) >>> { >>> - w

Re: OLL-core and Win10 [was Re: edition-editor usage]

Hi Trevor, Could you please post the *full* log and the input file? Then I can look into it. I recall having seen this error beforebut not what it was about. Urs Am 26. Dezember 2017 13:08:49 MEZ schrieb Jan-Peter Voigt : >Hi Trevor, > >I am working on Linux and have no Windows 10 running. I wi

Re: Re[2]: OLL-core and Win10 [was Re: edition-editor usage]

Am 26. Dezember 2017 20:17:33 MEZ schrieb Trevor : > >Hi Urs > >>Could you please post the *full* log and the input file? >>Then I can look into it. I recall having seen this error before but >not >>what it was about. >Thanks for looking! Source and log attached. The source is >example-1.ly f

Re: OLL-core and Win10 [was Re: edition-editor usage]

Am 26.12.2017 um 23:15 schrieb Trevor: Hi Urs OK, but I'm not at home right now, so it is somewhat hard to digest. Could you please send the log for a document that contains only  \include "oll-core/package.ily" ? Sure; it's quite bit shorter, so here it is inline: Starting lilypond-wind

Re: Re[2]: OLL-core and Win10 [was Re: edition-editor usage]

Am 27. Dezember 2017 13:27:09 MEZ schrieb Trevor : >Hi Urs > >> >>OK, at least now I know where (in the code) the problem is and recall >>that I fixed that once. Just to be sure: are you sure you you use the >>latest state of oll-core? OTOH, from the type of issue it may well be >a >>Windows q

Re: Web: Update GSoC pages (issue 338320043 by g...@ursliska.de)

Am 02.01.2018 um 12:34 schrieb lemzw...@googlemail.com: BTW, I plan to still mentor the two projects that I was already assigned to. Great! That was the idea behind moving forward in that drastic manner ;-) Aah, with `attic' you mean moving down the page, right?  Then please unearth my tw

Re: Web: Update GSoC pages (issue 338320043 by g...@ursliska.de)

Am 02.01.2018 um 17:23 schrieb pkx1...@gmail.com: https://codereview.appspot.com/338320043/diff/40001/Documentation/included/gsoc.itexi File Documentation/included/gsoc.itexi (right): https://codereview.appspot.com/338320043/diff/40001/Documentation/included/gsoc.itexi#newcode192 Docume

Re: OLL-core and Win10 [was Re: edition-editor usage]

Hi Trevor Am 27.12.2017 um 14:33 schrieb Urs Liska: Done; here's the log output: Starting lilypond-windows.exe 2.19.80 [Untitled]... Processing `C:/Users/tdani/AppData/Local/Temp/frescobaldi-u9vnw1qc/tmp4_jxjpvb/document.ly' Parsing... location: # initial path: C:/Users/tdani/openl

Re: OLL-core and Win10 [was Re: edition-editor usage]

Am 08.01.2018 um 14:50 schrieb David Kastrup: Urs Liska writes: Hi Trevor Am 27.12.2017 um 14:33 schrieb Urs Liska: Done; here's the log output: Starting lilypond-windows.exe 2.19.80 [Untitled]... Processing `C:/Users/tdani/AppData/Local/Temp/frescobaldi-u9vnw1qc/tmp4_jxjpvb/docume

Re: OLL-core and Win10 [was Re: edition-editor usage]

Am 08.01.2018 um 14:49 schrieb Karlin High: On 1/8/2018 7:16 AM, Urs Liska wrote: Could people on different Windows versions please compile the following file and tell me about the output? Windows 7 64-bit SP1: C:\Users\karlin\Music\LilyPond>lilypond ursliska-pathtest.ly GNU LilyP

Re: OLL-core and Win10 [was Re: edition-editor usage]

Am 08.01.2018 um 15:46 schrieb Karlin High: On 1/8/2018 8:25 AM, Urs Liska wrote: Could you please check if a) you can specify the path to the ly file with both forward and backward slashes b) this makes a difference in the output Windows 7 Pro 64-bit SP1 C:\Users\karlin\Music\LilyPond

Re: OLL-core and Win10 [was Re: edition-editor usage]

Am 08.01.2018 um 15:50 schrieb Urs Liska: I think I won't wait for feedback from users of Win 8, Vista or XP but simply fix it according to the current knowledge. I have now made some changes and pushed the to the "windows" branch of oll-core. I'm not 100% convince

Re: OLL-core and Win10 [was Re: edition-editor usage]

Am 08.01.2018 um 17:30 schrieb Karlin High: On 1/8/2018 10:11 AM, Urs Liska wrote: It would be great if some Windows users with Git access could fetch that branch and check it out. Which Git has this? GitHub? Savannah? Somewhere else? https://github.com/openlilylib/oll-core There are a

Re: OLL-core and Win10 [was Re: edition-editor usage]

Am 08.01.2018 um 18:11 schrieb Karlin High: Urs, was there supposed to be a "Windows" branch? Oops, obviously I only pushed the master branch again. Now the windows branch is on Github, sorry. Urs ___ lilypond-devel mailing list lilypond-devel@gnu

Fwd: FSF spring internship applicant looking for a GNU project

Is this something we would care about? Ursprüngliche Nachricht Von: Andrew Engelbrecht Gesendet: 26. Januar 2018 21:31:02 MEZ An: summer-of-c...@gnu.org Betreff: FSF spring internship applicant looking for a GNU project Hello GNU maintainers, The FSF tech team would like to o

Re: GSoC 2018 Interest and Information Request

Am 18. Februar 2018 20:46:37 MEZ schrieb Ed Harbison : >Hey Kieren! Thank you! > >Your background is very impressive. I’m glad to be talking to someone >as talented as you are. > >This project seems perfect to me to be honest. As I said, I was trying >to implement some of my own, so this is ex

Re: Web/Easier editing update

Am 28.02.2018 um 19:00 schrieb Simon Albrecht: Hi everybody, I noticed slight glitches when having a look at the ‘Easier editing’ page on the website. This is the text about Frescobaldi: > Frescobaldi is a lightweight, yet powerful, music and text editor with many features added and enhanc

Re: [GSoC 2018] Introduce myself

Hello Wang, Am 22.02.2018 um 12:39 schrieb Yijie Wang: Hi everyone, My name is Yijie Wang, I'm a Computer Science sophomore from Beijing Jiaotong University, China. I have knowledge of C++, Python and Java. Lilypond is a very useful tool for me and I would love to be a part of improving it.

Re: GSoC Follow-Up

Hi Ed, Am 01.03.2018 um 05:01 schrieb Kieren MacMillan: Hi Ed, I’d love to hear everyone’s opinions about doing a project with stylesheets, which seems to be the project I plan on applying with. What would everyone want to see in the project? I think I can piggy-back on Kieren's post to

Re: Allura/SourceForge to Gitlab migration

Am 9. April 2018 20:06:20 MESZ schrieb James Lowe : >Hello, > >On Mon, 9 Apr 2018 12:56:57 -0500, Karlin High >wrote: > >> On 4/9/2018 11:06 AM, Federico Bruni wrote: >> > >> > I don't want to revamp this old discussion: >> > >http://lists.gnu.org/archive/html/lilypond-devel/2013-10/msg00095.ht

Re: Allura/SourceForge to Gitlab migration

Am 09.04.2018 um 22:57 schrieb Federico Bruni: Il giorno lun 9 apr 2018 alle 22:23, Karlin High ha scritto: On 4/9/2018 3:05 PM, Karlin High wrote: Whether terms of service and such are aligned with GNU standards is something I haven't checked. ...But if projects like Debian and GNOME

Re: Allura/SourceForge to Gitlab migration

Am 09.04.2018 um 21:15 schrieb Carl Sorensen: On 4/9/18, 1:04 PM, "lilypond-devel on behalf of Urs Liska" wrote: Am 9. April 2018 20:06:20 MESZ schrieb James Lowe : >Hello, > >On Mon, 9 Apr 2018 12:56:57 -0500, Karlin High >wrot

Re: Allura/SourceForge to Gitlab migration

(CCing the list again) Am 10.04.2018 um 01:07 schrieb Carl Sorensen: On 4/9/18, 4:20 PM, "Urs Liska" wrote: Am 09.04.2018 um 21:15 schrieb Carl Sorensen: > On 4/9/18, 1:04 PM, "lilypond-devel on behalf of Urs Liska" wrote:

Re: Release schedule for 2.20

Am 9. Mai 2018 12:18:37 MESZ schrieb Aaron Hill : >On 2018-05-09 02:49, Malte Meyn wrote: >> But an increasing number of questions asked in forums or on the lists >> can be answered by “compile current master or wait for 2.21.0”. And a >> huge number of answers requires at least 2.19.xx but peopl

\class grob property

Hi all, I'm thinking about having a new grob property \class, but before digging deeper I'd like to put the idea up for discussion. This would have two different goals: 1) for SVG output the objects would get the class assigned (along with an id). I don't have any idea yet how that is implem

Re: \class grob property

Am 14.05.2018 um 00:02 schrieb David Kastrup: Urs Liska writes: Hi all, I'm thinking about having a new grob property \class, but before digging deeper I'd like to put the idea up for discussion. This would have two different goals: 1) for SVG output the objects would get

Re: \class grob property

Hi Harm, Am 14.05.2018 um 10:36 schrieb Thomas Morley: 2018-05-14 8:50 GMT+02:00 Urs Liska : Am 14.05.2018 um 00:02 schrieb David Kastrup: Urs Liska writes: Hi all, I'm thinking about having a new grob property \class, but before digging deeper I'd like to put the idea up for

Re: \class grob property

ay. Best Urs Am 17.05.2018 um 14:15 schrieb Paul Morris: Hi Urs, On 05/13/2018 02:02 PM, Urs Liska wrote: 1) for SVG output the objects would get the class assigned (along with an id). I don't have any idea yet how that is implemented, though. This will make it possible to work with C

Re: \class grob property

Am 17.05.2018 um 15:46 schrieb David Kastrup: Paul Morris writes: On 05/17/2018 09:00 AM, David Kastrup wrote: Man, I must have slept through this. "this is already supported in 2.19" is misleading if it's actually only supported _outside_ of 2.19, namely by chancing upon people in the kn

Re: Doc: document grob metadata in SVG output in Notation Reference (issue 357720044 by paulwmor...@gmail.com)

LGTM! ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: #5355 Doc: document grob metadata in SVG output in Notation Reference

Am 01.07.2018 um 09:55 schrieb James Lowe: I don't know what the difference is between pull and fetch in terms of 'rights' but I'd have thought it would be the same right? Yes, the difference comes only on your own computer. ___ lilypond-devel m

Re: xml2ly, a new translator from MusicXML to LilyPond

Am 1. September 2018 11:37:14 MESZ schrieb Victor Rouanet : >Le 01/09/2018 à 10:25, Menu Jacques a écrit : >> I only have read access to the github issue tracker yet. How can can >I >> get working access to it? >> >I guess you have to ask the repository owner to grant you the >appropriate perm

Re: xml2ly, a new translator from MusicXML to LilyPond

re >distributed using sourceforge file release system. > >JM > >> Le 1 sept. 2018 à 11:50, Urs Liska a écrit : >> >> >> >> Am 1. September 2018 11:37:14 MESZ schrieb Victor Rouanet >: >>> Le 01/09/2018 à 10:25, Menu Jacques a écrit : >&g

Re: xml2ly, a new translator from MusicXML to LilyPond

Am 1. September 2018 19:57:29 MESZ schrieb Menu Jacques : >Hello Urs, > > >> Maybe the best bet would be to create a small wrapper that uses the >library and can be deployed with LilyPond. > >Well, actually, xml2ly is such a wrapper. > Ah, I thought this could be the case immediately after I se

Re: Non-quadratic form of whiteout

Am 16.09.2018 um 15:19 schrieb Malte Meyn: Am 16.09.18 um 15:16 schrieb Kieren MacMillan: 3. at any other point on the grob, the whiteout should extend [horizontally and vertically] by an interpolated amount. How to interpolate? Maybe in such a way that a point or circle gets an elli

Re: Non-quadratic form of whiteout

Am 16.09.2018 um 15:44 schrieb Kieren MacMillan: Hi Urs, Am I getting something wrong here: why are you asking about intermediate points? Aren't we only interested in the whiteout around the outer edges? Consider the letter O, with 'outline #'(5 . 0). It’s easy to see that the thickness on

Re: Negative page numbers

Am 16. September 2018 21:28:26 MESZ schrieb Dan Eble : >> Real >> Page_breaking::page_height (int page_num, bool last) const >> { >> // The caches allow us to store the page heights for any >> // non-negative page numbers. We use a negative value in the >> // cache to signal that that posi

Limit the angle of broken hairpins

glad if someone could add the code to create the grob properties (should be little work but not if you have to first look everything up like me) in order to upload it for review later. Urs >From 500f284e6776eb90d389d378c0f92c7d02e5e9a0 Mon Sep 17 00:00:00 2001 From: Urs Liska Date: Tue, 1

Re: Problem with guile-2.9.1-prerelease

Am 11. Oktober 2018 20:17:45 MESZ schrieb Karlin High : >On 10/11/2018 12:59 PM, David Kastrup wrote: >> we should be able to add code that will run under all versions. > >The guile-devel post linked in the OP indicates that Guile 3 should >have >greatly improved performance over Guile 2. Maybe

  1   2   3   4   5   6   7   8   >