Re: LM 2.4.1: More accurate description of variable naming rules (issue 280560043 by address@hidden)

[dak]

https://codereview.appspot.com/280560043/diff/20001/Documentation/learning/common-notation.itely
File Documentation/learning/common-notation.itely (right):

https://codereview.appspot.com/280560043/diff/20001/Documentation/learning/common-notation.itely#newcode1343
Documentation/learning/common-notation.itely:1343: The name of a
variable must consist of alphabetic characters, underscores
I think that this is the wrong place for this description because you
are not talking about a "variable" but rather about LilyPond's idea of
identifiers.  Those are not just used for "variables" (which are usually
understood as music expressions) but for markup commands, note names,
layout/output settings, grob names, context names, context property
names, grob property names, music function names, engraver and
translator names, context modification names.  We have a number of
conventions for the various different kinds of identifiers here.

I don't think we are doing people a favor by dropping the definition of
the general identifier syntax here at the point music variables are
introduced without giving any guidance about what actually is commonly
used for what purpose.  That does not help in understanding other
people's files, and it does not help in writing one's own files in a
manner where others will get the intent without some double takes.

https://codereview.appspot.com/280560043/