Created new issue for the general #@var{variable} vs @var{variable}
discussion.
http://code.google.com/p/lilypond/issues/detail?id=4105
https://codereview.appspot.com/140630043/diff/1/Documentation/learning/tweaks.itely
File Documentation/learning/tweaks.itely (right):
https://codereview.appspot.com/140630043/diff/1/Documentation/learning/tweaks.itely#newcode453
Documentation/learning/tweaks.itely:453: \tweak
@var{layoutObject}.@var{layout-property} #@var{value}
On 2014/09/15 07:26:45, dak wrote:
The Google issue pointed out that this should be "LayoutObject" to
reflect the
proper case.
Done.
It is somewhat disconcerting that the Info page rendition (rather
than the HTML pages) will read LAYOUTOBJECT and LAYOUT-PROPERTY
anyway, as
that's the way @var placeholders are formatted. Still, I think
that's probably
the best we can do.
You put in #@var{value} instead of @var{value}. I think we are not
overly
consistent regarding that, but it is worth mentioning that something
like (see
Learning Manual in Tweaks)
\override TextSpanner.bound-details.left.text
= \markup { \small \bold Slower }
(can also be used as a tweak) gets along perfectly fine without a #
sign, so the
# is really an integral part of @var{value} and not part of the \tweak
syntax.
As per Trevor's suggestion I'll make a new tracker for dealing with the
inconsistencies in the doc.
https://codereview.appspot.com/140630043/
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
