Hi Jan-Peter (et al.),
> I am amazed what kind of discussion is raised on this topic :)
Me, too. Maybe we should have international music engraving conferences more
often than once every 20 years… ;)
> I'd suggest alternative commands to create something
> like an XQuery/CSS/whatever functiona
Am 21.01.20 um 18:50 schrieb Dan Eble:
> 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 V
Flaming Hakama by Elaine writes:
>> -- 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 Engrav
> -- 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, 202
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.
>
>
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 ma
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 speaks
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
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,
—
Dan
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
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" …
>
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:
>
>\c
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,
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 = choir.
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 { …
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
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
> \conte
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
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?)
> tha
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
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 the
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 abilit
Dan Eble writes:
> 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
> this:
>
> \context Staff = "along" {
> \cont
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
this:
\context Staff = "along" {
\context Voice = "B" {
...
24 matches
Mail list logo
