Re: Looking for help in configuring LilyDev in VirtualBox

Am 21.01.2020 um 20:44 schrieb Peter Toye: Re: Looking for help in configuring LilyDev in VirtualBox This time after the reboot I got the same result. No sharing of clipboard, no more processes. Tried closing VBox and restarting it, but same result. Try to start the client manually and see

Re: Context paths (and the Edition Engraver)

> -- Forwarded message -- > From: David Kastrup > To: Dan Eble > Cc: lilypond-devel@gnu.org > Bcc: > Date: Tue, 21 Jan 2020 22:51:29 +0100 > Subject: Re: Context paths (and the Edition Engraver) > Dan Eble writes: > > > On Jan 21, 2020, at 14:37, David Kastrup wrote: > >> > >>

Re: guile-3.0 and LilyPond - here: /input/regression/context-defaultchild-cycle.ly fails

Thomas Morley writes: > Am Mi., 22. Jan. 2020 um 00:59 Uhr schrieb David Kastrup : >> >> >> #(ly:set-option 'warning-as-error #t) >> %% not sure why these warnings appear twice [dfe] >> -#(ly:expect-warning (_ "default child context begins a cycle: `~a'") 'Score) >> -#(ly:expect-warning (_

Re: guile-3.0 and LilyPond - here: /input/regression/context-defaultchild-cycle.ly fails

Am Mi., 22. Jan. 2020 um 00:59 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Hi, > > > > some remarks: > > > > Guile-3.0 > > First I compiled successfully guile-master from their repo, giving GNU > > Guile 3.0.0.6-f3298 > > Trying to compile LilyPond with that guile (ofcourse adding

Re: guile-3.0 and LilyPond - here: /input/regression/context-defaultchild-cycle.ly fails

Thomas Morley writes: > Hi, > > some remarks: > > Guile-3.0 > First I compiled successfully guile-master from their repo, giving GNU > Guile 3.0.0.6-f3298 > Trying to compile LilyPond with that guile (ofcourse adding a bunch of > patches) I had some problems pointing configure to the correct

Re: guile-3.0 and LilyPond - here: /input/regression/context-defaultchild-cycle.ly fails

Am Mi., 22. Jan. 2020 um 00:41 Uhr schrieb Karlin High : > > On 1/21/2020 5:10 PM, Thomas Morley wrote: > > Afterwards I've got a successful ´make´ with current LilyPond-master. > > So it's a functional LilyPond with guile-3.0? How does it perform if fed > something big? I'm thinking of the thread

Re: guile-3.0 and LilyPond - here: /input/regression/context-defaultchild-cycle.ly fails

On 1/21/2020 5:10 PM, Thomas Morley wrote: Afterwards I've got a successful ´make´ with current LilyPond-master. So it's a functional LilyPond with guile-3.0? How does it perform if fed something big? I'm thinking of the thread on benchmarking that used Vaughan McAlley's MDSM.ly, the Robert

guile-3.0 and LilyPond - here: /input/regression/context-defaultchild-cycle.ly fails

Hi, some remarks: Guile-3.0 First I compiled successfully guile-master from their repo, giving GNU Guile 3.0.0.6-f3298 Trying to compile LilyPond with that guile (ofcourse adding a bunch of patches) I had some problems pointing configure to the correct guile and guile-config to the correct

Re: Context paths (and the Edition Engraver)

Dan Eble writes: > On Jan 21, 2020, at 14:37, David Kastrup wrote: >> >> StaffGroup = "organ" . Staff = "upper" . Voice . SubVoice = 2 > > OK. It would be an understandable growth on the current face of LilyPond. :) > > Questions follow, but I'm not asking you to spend time investigating. > >

Re: Context paths (and the Edition Engraver)

On Jan 21, 2020, at 14:37, David Kastrup wrote: > > StaffGroup = "organ" . Staff = "upper" . Voice . SubVoice = 2 OK. It would be an understandable growth on the current face of LilyPond. :) Questions follow, but I'm not asking you to spend time investigating. Do you think we could achieve

Re: Context paths (and the Edition Engraver)

On 1/21/20, 12:32 PM, "Dan Eble" wrote: On Jan 21, 2020, at 14:02, Carl Sorensen wrote: > It seems to me that > > \context StaffGroup ID1.ID2.ID3.ID4 ... > ID4 must be a bottom context Please guide me step by step to this conclusion. All this example

Re: Looking for help in configuring LilyDev in VirtualBox

Tuesday, January 21, 2020, 6:24:25 PM, Michael Käppler wrote: Am 21.01.2020 um 11:13 schrieb Peter Toye: Re: Looking for help in configuring LilyDev in VirtualBox Monday, January 20, 2020, 10:24:13 PM, you wrote: Am 20.01.2020 um 16:04 schrieb Peter Toye: Re: Looking for help in configuring

Re: Context paths (and the Edition Engraver)

Dan Eble writes: > On Jan 21, 2020, at 14:20, David Kastrup wrote: >> >>> Notation borrowed directly from them will not integrate well >>> into LilyPond, but it might be fruitful to ask how we could modify >>> expressions like these to fit in. > ... >> The syntax appears not to be a good match

Re: Context paths (and the Edition Engraver)

On Jan 21, 2020, at 14:02, Carl Sorensen wrote: > It seems to me that > > \context StaffGroup ID1.ID2.ID3.ID4 ... > ID4 must be a bottom context Please guide me step by step to this conclusion. All this example speaks to me is that ID4 is a great-grandchild of ID1. Thanks and regards, —

Re: Context paths (and the Edition Engraver)

On Jan 21, 2020, at 14:20, David Kastrup wrote: > >> Notation borrowed directly from them will not integrate well >> into LilyPond, but it might be fruitful to ask how we could modify >> expressions like these to fit in. ... > The syntax appears not to be a good match to LilyPond even though the

Re: Context paths (and the Edition Engraver)

Dan Eble writes: > On Jan 21, 2020, at 11:31, Jan-Peter Voigt wrote: >> I'd like that, though it would be a quite invasive change. >> And if we stay with the string for the context id and then use >> lists/paths in the \context statement like >> \new Staff = "choir" << \new Voice = "soprano" …

Re: Context paths (and the Edition Engraver)

Hi all, > I don't think anyone was suggesting that a context ID would include the IDs > of its parents as a substring. At least I wasn't trying to suggest that. The > idea is that something like this: > >\context foo.bar.baz { … } > > Could be interpreted as shorthand for this: > >

Re: Context paths (and the Edition Engraver)

Hi all, > \new ChoirStaff = choir << >\new Staff = choir.upper << >\new Voice = choir.upper.soprano >\new Voice = choir.upper.alto > >> > \new Staff = choir.lower << >\new Voice = choir.lower.tenor >\new Voice = choir.lower.bass > >> > >> To be honest,

Re: Context paths (and the Edition Engraver)

On Jan 21, 2020, at 14:02, Carl Sorensen wrote: > \new ChoirStaff = choir << >\new Staff = choir.upper << >\new Voice = choir.upper.soprano >\new Voice = choir.upper.alto >>> > \new Staff = choir.lower << >\new Voice = choir.lower.tenor >\new Voice =

Re: Context paths (and the Edition Engraver)

On 1/21/20, 11:19 AM, "lilypond-devel on behalf of Dan Eble" wrote: On Jan 21, 2020, at 11:31, Jan-Peter Voigt wrote: > > \context Voice = choir.soprano > > it would be inconsistent with \new = "…" The implied example \new Voice = choir.soprano {

Re: Janek is coming back to LilyPond! :-)

Hi Janek, 1. Wonderful to have you back! 2. There’s this lyrics thing maybe you could take a look at…? ;) Best, Kieren. Kieren MacMillan, composer (he/him/his) ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info

Re: Looking for help in configuring LilyDev in VirtualBox

Am 21.01.2020 um 11:13 schrieb Peter Toye: Re: Looking for help in configuring LilyDev in VirtualBox Monday, January 20, 2020, 10:24:13 PM, you wrote: Am 20.01.2020 um 16:04 schrieb Peter Toye: Re: Looking for help in configuring LilyDev in VirtualBox Monday, January 20,

Re: Context paths (and the Edition Engraver)

On Jan 21, 2020, at 11:31, Jan-Peter Voigt wrote: > > \context Voice = choir.soprano > > it would be inconsistent with \new = "…" The implied example \new Voice = choir.soprano { … } could be given a consistent interpretation. For example, it could be interpreted as creating \new Voice

Re: Context paths (and the Edition Engraver)

On Jan 21, 2020, at 11:31, Jan-Peter Voigt wrote: > I'd like that, though it would be a quite invasive change. > And if we stay with the string for the context id and then use > lists/paths in the \context statement like > \new Staff = "choir" << \new Voice = "soprano" … > > and then use >

Re: Context paths (and the Edition Engraver)

Hi Carl, > All of this discussion about including the edition engraver and packages in > LilyPond core is exciting to me. +1 > I think that if we choose to do so, it should represent a major release for > LilyPond, i.e. it should become LilyPond 3.0 If we really get a great extension/package

Re: Context paths (and the Edition Engraver)

Hi Jan-Peter, >> Not sure how much of a "crowd" we are… ;) > at least we are 2 :) Well, how many more until we gain official "crowd" status? =) >> I agree on both points. (Perhaps one of my first contributions in 2020 >> should be a less-ambiguous set of documented examples for the EE?) >

PATCHES - Countdown for January 21st

Hello, Here is the current patch countdown list. The next countdown will be on January 23rd. A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ Push: 5663 Encoding preparations for Python 3.5 - Jonas Hahnfeld

Re: Context paths (and the Edition Engraver)

On 1/19/20, 2:42 PM, "lilypond-devel on behalf of Dan Eble" wrote: One of the things in Kieren's intro to the Edition Engraver (EE) that resonated with me was the context paths. His example was something like `singwithbach.along.Voice.B`, which was supposed to refer to something like

Re: Context paths (and the Edition Engraver)

Hi there, > [Single-level quotes are David Kastrup’s; double-level quotes are Dan Eble’s.] > >> Comments from the EE crowd? > > Not sure how much of a "crowd" we are… ;) at least we are 2 :) >>> One of the things in Kieren's intro to the Edition Engraver (EE) that >>> resonated with me was

Re: packaging lilypond as a docker container?

Would be happy to try the Dockerfile, since I've never used Docker before and find the concept interesting. Could you push your changes to your LilyDev fork and/or file a pull request against Federico's repo? Cheers, Michael Am 21.01.2020 um 16:47 schrieb Dan Eble: On Jan 20, 2020, at 18:21,

Re: packaging lilypond as a docker container?

On Jan 20, 2020, at 18:21, Karlin High wrote: > > There already is a LilyDev Docker image. > > > > I tried it once, but was unable to get it working. It was my first and only > experience with Docker, so that's probably my fault. I was

Re: github mirror of lilypond?

> A problem with the policy "trivial things can just be pushed" is > that "trivial" is open for interpretation. Of course, but this shouldn't be a hindrance. > Even a change that was intended to affect only comments could have a > bad impact if, say, it inserts an accidental stray character

Re: github mirror of lilypond?

Dan Eble writes: > On Jan 20, 2020, at 11:51, pkx1...@posteo.net wrote: >> >> On 20/01/2020 16:16, Werner LEMBERG wrote: Trivial things from a developer with push access can be just pushed. Complex or otherwise contential things warrant a chance for developers to take a look at

Re: Document C++ structs for slur scoring (issue 571380043 by hanw...@gmail.com)

LGTM. Thanks. https://codereview.appspot.com/571380043/

Re: lily: fix some type conversion warnings (issue 557190043 by hanw...@gmail.com)

https://codereview.appspot.com/557190043/diff/581490044/lily/pointer-group-interface.cc File lily/pointer-group-interface.cc (right): https://codereview.appspot.com/557190043/diff/581490044/lily/pointer-group-interface.cc#newcode30 lily/pointer-group-interface.cc:30: return arr ? int

Re: document and test slur score debugging (issue 555160043 by hanw...@gmail.com)

https://codereview.appspot.com/555160043/diff/577340043/input/regression/slur-inspect-quants.ly File input/regression/slur-inspect-quants.ly (right): https://codereview.appspot.com/555160043/diff/577340043/input/regression/slur-inspect-quants.ly#newcode3

Re: packaging lilypond as a docker container?

On Mon, Jan 20, 2020 at 10:05:23PM +, Carl Sorensen wrote: > > Wouldn't it be much more simple to build lilypond as a Docker application? > > I don't know anything about building lilypond as a Docker application. If it > were possible to execute a docker application from the

Re: github mirror of lilypond?

On Jan 20, 2020, at 11:51, pkx1...@posteo.net wrote: > > On 20/01/2020 16:16, Werner LEMBERG wrote: >>> Trivial things from a developer with push access can be just pushed. >>> Complex or otherwise contential things warrant a chance for >>> developers to take a look at it. "Half a chance" seems

Re: Clean up and document include file searching (issue 573400043 by hanw...@gmail.com)

https://codereview.appspot.com/573400043/diff/549420043/lily/sources.cc File lily/sources.cc (right): https://codereview.appspot.com/573400043/diff/549420043/lily/sources.cc#newcode60 lily/sources.cc:60: Sources::find_full_path(string file_string, string const _dir) Is there any reason not to

Re: github mirror of lilypond?

On Jan 20, 2020, at 11:40, Carl Sorensen wrote: > I agree. And while comments during countdown are annoying and frustrating, > it's even more annoying and frustrating to have a commit reverted. So I > prefer countdown to reversion. +1 — Dan

Re: Context paths (and the Edition Engraver)

Hi all, [Single-level quotes are David Kastrup’s; double-level quotes are Dan Eble’s.] > Comments from the EE crowd? Not sure how much of a "crowd" we are… ;) >> One of the things in Kieren's intro to the Edition Engraver (EE) that >> resonated with me was the context paths. […] >> The

Option handling

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

Re: Document C++ structs for slur scoring (issue 571380043 by hanw...@gmail.com)

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

Re: packaging lilypond as a docker container?

> Almost exactly a year ago, there was a sizable "Please test gub" > effort initiated by Knut Petersen. By the way: Any idea what has happened with Knut? He doesn't respond even to private e-mails since a few months... Werner

Document C++ structs for slur scoring (issue 571380043 by hanw...@gmail.com)

Very nice, thanks! https://codereview.appspot.com/571380043/

Re: remove obsolete lines from lily-guile-macros.hh (issue 555170043 by hanw...@gmail.com)

LGTM https://codereview.appspot.com/555170043/

Re: packaging lilypond as a docker container?

Jonas Hahnfeld writes: > Am Dienstag, den 21.01.2020, 11:28 +0100 schrieb David Kastrup: >> >> Windows really is the elephant in the room. MacOSX will cater with >> native port systems like MacPorts etc and other UNIX-like systems >> also have working packagers and package systems. > > So if I

Re: packaging lilypond as a docker container?

Am Dienstag, den 21.01.2020, 11:28 +0100 schrieb David Kastrup: > Jonas Hahnfeld < > hah...@hahnjo.de > > writes: > > > Am Dienstag, den 21.01.2020, 02:38 -0600 schrieb Karlin High: > > > On 1/21/2020 1:49 AM, Han-Wen Nienhuys wrote: > > > > if GUB is used, who is maintaining and/or working on

Re: packaging lilypond as a docker container?

Jonas Hahnfeld writes: > Am Dienstag, den 21.01.2020, 02:38 -0600 schrieb Karlin High: >> On 1/21/2020 1:49 AM, Han-Wen Nienhuys wrote: >> > if GUB is used, who is maintaining and/or working on it? >> >> Almost exactly a year ago, there was a sizable "Please test gub" effort >> initiated by

Re: Packages/modules

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. > > * if the requested package/module is

Re: Looking for help in configuring LilyDev in VirtualBox

Monday, January 20, 2020, 10:24:13 PM, you wrote: Am 20.01.2020 um 16:04 schrieb Peter Toye: Re: Looking for help in configuring LilyDev in VirtualBox Monday, January 20, 2020, 10:26:55 AM, you wrote: Am 20.01.2020 um 11:08 schrieb Peter Toye: Re: Looking for help in configuring LilyDev in

remove obsolete lines from lily-guile-macros.hh (issue 555170043 by hanw...@gmail.com)

LGTM https://codereview.appspot.com/555170043/

Re: packaging lilypond as a docker container?

Am Dienstag, den 21.01.2020, 02:38 -0600 schrieb Karlin High: > On 1/21/2020 1:49 AM, Han-Wen Nienhuys wrote: > > if GUB is used, who is maintaining and/or working on it? > > Almost exactly a year ago, there was a sizable "Please test gub" effort > initiated by Knut Petersen. > > < >

Re: packaging lilypond as a docker container?

On 1/21/2020 1:49 AM, Han-Wen Nienhuys wrote: if GUB is used, who is maintaining and/or working on it? Almost exactly a year ago, there was a sizable "Please test gub" effort initiated by Knut Petersen. Clear

Re: document and test slur score debugging (issue 555160043 by hanw...@gmail.com)

LGTM, thanks! https://codereview.appspot.com/555160043/