Hi, The to-barline property of hairpins and other spanners is incredibly helpful, and greatly improves the look of my scores. But spelling "barline" as a single word conflicts with the two-word spelling that appears more frequently throughout the code, especially in the spelling of the BarLine grob, with which users interact frequently:
%%% BEGIN %%% *355 occurrences as two separate words:* lilypond-2.25.19$ clear; ack --no-filename -o '\b\w*BarLine\w*\b' | sort | uniq -c 75 BarLine 3 currentBarLine 4 defineBarLine 16 forbidBreakBetweenBarLines lilypond-2.25.19$ clear; ack --no-filename -o '\b\w*bar-line\w*\b' | sort | uniq -c 254 bar-line 3 bar-lines *92 occurrences a compound word:* lilypond-2.25.19$ clear; ack --no-filename -o '\b\w*Barline\w*\b' | sort | uniq -c 7 Barline 2 cancelBeforeBarline 6 hairpinToBarline lilypond-2.25.19$ clear; ack --no-filename -o '\b\w*barline\w*\b' | sort | uniq -c 9 add_barline 49 barline 4 barline_color 5 barlines 6 nobarlines 4 prev_barline %%% END %%% Can the spelling of to-barline be changed to to-bar-line to better match the rest of the code? -- Trevor Bača www.trevorbaca.com soundcloud.com/trevorbaca
