James, you wrote Monday, September 15, 2014 5:52 PM
> On 15/09/14 16:04, d...@gnu.org wrote:
> [snip]
>> which, uh, points to @var{value} being quite in the minority, and the
>> text "@var{value} is a Scheme object, which is why it must be preceded
>> by" further muddifies the distinction between # being part of the
>> override/tweak syntax and part of the value.
>>
>> Also Documentation/notation/changing-defaults.itely contains quite a
>> few old-syntax overrides.
>>
>> I have to admit that putting @var{value} here alone will not help
>> consistency: this would need a more sweeping revision that replaces
>> "must be preceded by #" with "will usually be a Scheme value
>> introduced with # unless it is a LilyPond-native construct like a
>> markup".
>
> Do you have any particular preference this being the Learning Manual and
> all?
I'd keep the # for this amendment and raise a new doc issue to cover the
points David makes above.
Trevor
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
