Paul Crabbe <[email protected]> writes:

> 24 oct. 2026 15:45:43 David Kastrup <[email protected]>:

>> The propagation rules of \relative are basically:
>> { ... } the last pitch in the set propagates as the reference outside
>> << ... >> the last pitch in the set propagates as the reference outside
>> < ... > the first pitch in the set propagates as the reference outside
>> 
>> Apparently you are imagining yet another scheme
>> 
>> << ... >> no propagation of relative pitch happens inside, every element
>> inside starts with the outside reference pitch which presumably is also
>> what gets passed outside unmodified at the end.
>> 
>> Would be an idea, but that ship has sailed.  Too much historic baggage.
>
> Thank you for clarify this, I was not aware of the {...} and <<  
> ... >> propagation rules.

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 ...

If we can find great completions for that sentence, it may save us a lot
of work.

-- 
David Kastrup

Reply via email to