Re: [GLISS] Existing syntax abominations

[Trevor Daniels]

David Kastrup wrote Friday, September 21, 2012 5:46 PM

> Well, the host of different syntaxes to \tempo aside, here are some
> other nuisances:
[snip]
> Look and behold: after the closing brace of the sequential music, the
> expression is not finished because LilyPond has to see whether there is
> an \addlyrics after that, as it would become part of the expression.
> 
> So \addlyrics is on my blacklist of unnecessarily surprising constructs.

I take the point, but it would be a shame to ditch \addlyrics.  I'm sure
many users setting simple songs use this construct.

> Another parser baddy is \alternatives since it means that no \repeat
> expression can be considered complete without checking for potentially
> following alternatives.  It would make more sense if the alternatives
> were written _inside_ of the repeat.  Much more sense actually.

I fully agree.
 
> Then we have \override Grob #'this #'that = 7 which needs to get
> reverted with \revert Grob #'(this that) rather counter-intuitively, to
> the degree that people complain about a recently introduced warning
> resulting from \revert Grob #'this #'that (which never did what people
> thought it would, ignoring all but the first Scheme expression).

I agree with this too.

> Then strings in lyrics are sufficiently differently delimited from the
> way strings in markups are.  For example, they can contain unquoted
> curly braces in some positions.  In my opinion, lyrics (which can be
> interspersed with durations) have even less business to allow curly
> braces as part of words without using quote marks than markups have.

And with this.

Trevor