Le 20/11/2022 à 16:11, Lukas-Fabian Moser a écrit :
Thank you very much - this works from 2.23.8 on, I assume because of Dan's additions. Great!
There have been so many changes to bar lines that I have stopped tracking which happened in which version :-)
I still have to read up on the bar type definition codes which I never actually managed to understand. For example, in scm/bar-line.scm, I read:;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; predefined bar lines ;; ;; definition of bar lines goes as follows: ;; ;; (define-bar-line "mid-line bar[-annotation]" ;; "end-of-line bar[-annotation]" ;; "beginning-of-line bar[-annotation]" ;; "span bar") ;; ;; Each argument must be a string or #f. The string "" calls for a ;; zero-width stencil. The string "x" or the value #f call for no ;; stencil. "x" may be annotated, unlike #f.From this explanation, it find it hard to understand the the "mid-line" bar is taken as kind of an "identifier", which becomes clear only after reading(define-public (define-bar-line bar-glyph eol-glyph bol-glyph span-glyph) "Define a bar glyph @var{bar-glyph} and its substitutes at the end of a line (@var{eol-glyph}), at the beginning of a line (@var{bol-glyph}) and as a span bar (@var{span-glyph}). The substitute glyphs may be either strings or booleans: @code{#t} calls for the same value as @var{bar-glyph} and @code{#f} calls for no glyph."
Yes, the bar line system is slightly surprising: the "mid-line" part is used both as the argument to \bar and as the source for the mid-line glyph.
Also, "each argument must be a string or #f" seems strange when reading (define-bar-line "|" #t #f #t)So probably the comments on predefined bar lines don't reflect very faithfully what's actually happening?
This one looks like an oversight in commit 66c0227700. Cheers, Jean
OpenPGP_signature
Description: OpenPGP digital signature