[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Context paths (and the Edition Engraver)

From: Dan Eble
Subject: Re: Context paths (and the Edition Engraver)
Date: Tue, 21 Jan 2020 16:27:05 -0500

On Jan 21, 2020, at 14:37, David Kastrup <address@hidden> 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 making the quotes optional for some simple IDs, 
and making the whitespace optional?


In a situation where the user didn't care to constrain the context types, do 
you think could they be omitted, or would we have to invent a placeholder?


Maybe--MAYBE--I'm not yet advocating it, but maybe we could allow some 
ambiguity when there is no equal sign, and define how LilyPond resolves it; 
like if it is a context type then it is used as the context type, otherwise it 
is used as an ID, which would allow things like this:


> Does this give us a hook into making \set, \override and/or \tempo a
> music function in the long run?  Less than sure about that.
> Particularly \tempo appears rather tricky.

If I ever knew enough about the implementation of those to answer, I've 
forgotten it.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]