Re: Some "Cheat cheet" nitpicks

[David Kastrup]

Graham Percival <address@hidden> writes:

> On Wed, Dec 16, 2009 at 2:02 PM, Werner LEMBERG <address@hidden> wrote:
>>>> The best solution is probably to add a new command line option
>>>> `--default-left-padding' to lilypond-book (which is then used in
>>>> the Makefile with value 0mm to override the default setting of
>>>> 3mm), and adding a snippet option `left-padding' to the lilypond
>>>> environments (within lilypond-book) to override the default left
>>>> padding if necessary.
>>>
>>> No.  We're not adding that option to 90% of the snippets in the
>>> docs.  It can't be done automatically, and it's way too much work to
>>> do it manually.
>>
>> ???  I've just suggested the `--default-left-padding' option to
>> exactly avoid that!  Ideally, we would simply change the default value
>> of lilypond-book's `--left-padding' option to 0mm, but this breaks
>> backwards compatibility.  Thus my suggestion to have a means to
>> control the default value instead.
>
> If the makefile sets it to 0mm, then what happens for longer examples
> with bar numbers?  Presumably somebody needs to go through all the
> docs to find multi-line examples, then add
>    [left-padding=3mm]
> to those examples.
>
> This is too much work for not enough payoff.  Especially since (I
> think) a one-line patch to the C file that Sven identified would
> render this work unnecessary.

It is common to have the first line of multiple lines indented and
adjusted (they look like paragraphs essentially), but it makes little
sense to indent single lines.  In particular if you interchange single
lines with text, or treat them as inline material.

So it might be nice to be able to specify special padding/adjustment for
single-line formatting.  If there was a way to find out post-fact what
kind of formatting was actually employed for any snippet, this might
also be nice.  But one can probably guess somewhat reliably by checking
the width of the result.

-- 
David Kastrup