>> But I still think that there's a problem with \fill-line. I
>> don't think it should cause the word "Composer" to protrude
>> past the end of the staff when there is plenty of room for it
>> to fit properly right-aligned to the end of the staff.
>>
>> Yes, this is definitely a flaw in the current implementation of
>> \fill-line.
I don't think so. IMHO it's rather that the documentation of
`\fill-line` is not adequate to what this function really does, namely
to split a line into N equally large regions for N arguments, with the
text in the leftmost region left-aligned, the text in the rightmost
region right-aligned, and the remaining text strings centered in the
respective regions. In many cases it is plain ugly if the middle part
is moved to the right because the left part is little bit longer.
Consider this example.
```
\version "2.25.25"
\markup \fill-line {
"Fill line"
\fontsize #10 \bold "Title"
"Right" }
{ f' }
\markup \fill-line {
"Fill liiiiiiiiiiiiiiiiiiiiine"
\fontsize #10 \bold "Title"
"Right" }
{ g' }
\markup \justify-line{
"Justify line"
\fontsize #10 \bold "Title"
"Right" }
{ a' }
\markup \justify-line{
"Justify liiiiiiiiiiiiiiiiiiiiine"
\fontsize #10 \bold "Title"
"Right" }
{ b' }
\paper {
ragged-right = ##f
indent = 0
}
```
I most certainly want the current behaviour of `\fill-line` for such a
thing.
> This being the case, should a bug be added to the bug tracker? And
> if so, should I do it? Or would it be better if someone else did?
For a variant of `\fill-line` we already have an issue:
https://gitlab.com/lilypond/lilypond/-/issues/1234
[Actually, I now think it should be closed – we have `\justify-line`,
which does exactly what is requested AFAICS, but please comment there
if you have a different opinion.]
However, for these two
* Improve documentation of `\fill-line`.
* The default `\bookTitleMarkup` should be made more sophisticated,
recognizing that `\fill-line` should be called with only two
arguments if the middle element (i.e., `header:instrument`) is
empty.
we don't have issues, so yes, please add two new ones, also adding
code and images to show what's going on.
Werner
