On Sat, Oct 24, 2026 at 8:34 AM David Kastrup <[email protected]> wrote:

>
> Ok, now I am likely getting into troubled water with my sailed ship
> but...
>
> I distinctly remember that of all the \relative behavior it took by far
> the longest time for me to understand << ... >> behavior, and that in
> spite of it being actually exactly the same as for { ... } (apart from
> some stone-age compatibility option that may no longer exist).
>
> And the reason was that for { ... } the behavior makes sense.  For
> << ... >> it doesn't.  Why should any part in << ... >> get to influence
> any other part?  So it makes sense to all start them with the initial
> \relative reference.  And with regard to the outgoing pitch: there might
> be a weak incentive to the first track for conveying \relative outside
> (the dedicated survivor track), but it may actually just be least
> contrived to bounce out the original reference unchanged.
>
> So yes, it would really simplify things and likely take quite a bit of
> confusion potential out of \relative.  But it would be a bear of a
> change affecting basically all documents and needing to get taught to
> LilyPond code parsing libraries that also make Frescobaldi its job.
>
> Anybody care for filling in the following sentence?
>
> Even if we were starting from scratch, the current defaults are for the
> best because ...
>

Unless I am misunderstaing you, I would say that the currecnt defaults are
*less* confusing, because then the rule is, "Everything inside a relative
block is relative" instead of, "Everything is relative, except for when
there is a new vioce, at which time it reverts to the initial note, which
can be the explicit note you write after \relative or the first note you
write in the block."

Also, for me at least, it would break a lot of muscle memory built up over
the years.  I would be saying, "What's the first note in this \relative
block again?" a lot.  My 2 cents.

--
Knute Snortum

Reply via email to