LilyIssues / Issues / #4717 LM 2.4.1: More accurate description of variable naming rules

#4717 LM 2.4.1: More accurate description of variable naming rules

Status: Verified

Owner: Simon Albrecht

Labels: Fixed_2_19_36 (24)

Needs:

Patch:

Type: Documentation

Updated: 2016-03-06

Created: 2015-12-29

Creator: Simon Albrecht

Private: No

The previous wording was incorrect in disallowing dashes and underscores in principle. I took this more verbose explanation from a suggestion by Johan Vromans, which shows more of the possibilities currently available. I didn't include the part to disclose the more confusing, much debated syntax with double quotes. See http://lists.gnu.org/archive/html/lilypond-user/2015-12/msg00656.html &c.

https://codereview.appspot.com/280560043

Discussion

Anonymous - 2015-12-29

Patch: new --> needs_work
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2015-12-29

Comments in Reitveld.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Simon Albrecht - 2016-01-03

Patch: needs_work --> new
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Simon Albrecht - 2016-01-03

Completely redone: https://codereview.appspot.com/284070043

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2016-01-04

Passes make, make check and a full make doc.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2016-01-04

Patch: new --> review
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2016-01-06

Patch on countdown for Jan 9th

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2016-01-06

Patch: review --> countdown
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2016-01-09

Patch: countdown --> push
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2016-01-09

Patch counted down - please push

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2016-01-11

labels: --> Fixed_2_19_36

status: Started --> Fixed

Patch: push -->
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2016-01-11

author Simon Albrecht simon.albrecht@mail.de
Mon, 11 Jan 2016 17:40:42 +0000 (17:40 +0000)
committer James Lowe pkx166h@gmail.com
Mon, 11 Jan 2016 17:41:18 +0000 (17:41 +0000)
commit 42cd2e57e37cbbf1fc5ccbe2bc83048761690f60

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Simon Albrecht - 2016-03-02

status: Fixed --> Verified
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Phil Holmes - 2016-03-04

Simon - as a general rule we don't verify our own patches. It's obviously slightly different here, since James was the actual committer - but I just thought you might like to be reminded.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Simon Albrecht - 2016-03-06

Silly of me to not think of that, and thanks indeed for the reminder.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

LM 2.4.1: More accurate description of variable naming rules

Issue Tracker for LilyPond

Searches

Help

#4717 LM 2.4.1: More accurate description of variable naming rules

Discussion