Comment #11 on issue 1670 by d...@gnu.org: Allow numbers in variable names:
violin1mvt2 = c'
http://code.google.com/p/lilypond/issues/detail?id=1670
And now for a somewhat hilarious side-effect of Issue 2024:
$identifier-in-Scheme-syntax
is pretty much equivalent to what you would want here
Comment #10 on issue 1670 by d...@gnu.org: Allow numbers in variable names:
violin1mvt2 = c'
http://code.google.com/p/lilypond/issues/detail?id=1670
Fine modest proposal. But customHtuning is harder to read/type. I'd have
chosen a different name, but to be fair: this variable is only used
Comment #9 on issue 1670 by k-ohara5...@oco.net: Allow numbers in variable
names: violin1mvt2 = c'
http://code.google.com/p/lilypond/issues/detail?id=1670
Accidentally, this leaked into in the draft 2.15.16 user manual:
The previous example could also be written as follows:
"custom-tun
Werner LEMBERG writes:
>>> Not just for section but also for bar numbers.
>>> ThemeFromBarsThirtyTwoToSixtyFour versus theme32-64. Numbers are
>>> easier to grasp with the eye than words.
>>
>> And so you silently demand dashes in variable names as well...
>
> Assuming that we allow Unicode cha
>> Not just for section but also for bar numbers.
>> ThemeFromBarsThirtyTwoToSixtyFour versus theme32-64. Numbers are
>> easier to grasp with the eye than words.
>
> And so you silently demand dashes in variable names as well...
Assuming that we allow Unicode characters in variable names in the
lilyp...@googlecode.com writes:
> Comment #8 on issue 1670 by j...@sente.ch: Allow numbers in variable
> names: violin1mvt2 = c'
> http://code.google.com/p/lilypond/issues/detail?id=1670
>
> To state a user opinion (I'm in jazz). It would be very very helpful
> to have numbers in variables. I've b
Comment #8 on issue 1670 by j...@sente.ch: Allow numbers in variable names:
violin1mvt2 = c'
http://code.google.com/p/lilypond/issues/detail?id=1670
To state a user opinion (I'm in jazz). It would be very very helpful to
have numbers in variables. I've been missing that since I use lilypond
Werner LEMBERG gnu.org> writes:
> > (Accented characters are also accepted, but that's not documented an
> > probably not a good idea either.)
>
> Why not? Since lilypond accepts UTF-8 only, I don't see any problem,
> except unveiling potential guile bugs.
>
Why not? Only because the capabil
Comment #7 on issue 1670 by percival.music.ca: Allow numbers in variable
names: violin1mvt2 = c'
http://code.google.com/p/lilypond/issues/detail?id=1670
there are some interesting ideas here. I've added them to the GLISS list,
and we will discuss them in due course.
> (Accented characters are also accepted, but that's not documented an
> probably not a good idea either.)
Why not? Since lilypond accepts UTF-8 only, I don't see any problem,
except unveiling potential guile bugs.
Werner
___
bug-lilypond mailin
> Comment #6 on issue 1670 by carl.d.s...@gmail.com: Allow numbers in
> variable names: violin1mvt2 = c'
>
> Our language has a well-defined rule for variables: letters only.
Just to be pedantic:
letters only, and not a note-name in the current input language.
Actually, you can use a note-nam
Comment #6 on issue 1670 by carl.d.s...@gmail.com: Allow numbers in
variable names: violin1mvt2 = c'
http://code.google.com/p/lilypond/issues/detail?id=1670
I understand. But that gives one more special case: "You don't normally
need to put quotes around the variable name in a variable de
lilyp...@googlecode.com writes:
> Comment #5 on issue 1670 by k-ohara5...@oco.net: Allow numbers in
> variable names: violin1mvt2 = c'
> http://code.google.com/p/lilypond/issues/detail?id=1670
>
>> I think requiring quotes around variable definitions in order to
>> allow numbers would be a mistake
Comment #5 on issue 1670 by k-ohara5...@oco.net: Allow numbers in variable
names: violin1mvt2 = c'
http://code.google.com/p/lilypond/issues/detail?id=1670
I think requiring quotes around variable definitions in order to allow
numbers would be a mistake.
Just to be clear, only definitions
Comment #4 on issue 1670 by tdaniels...@googlemail.com: Allow numbers in
variable names: violin1mvt2 = c'
http://code.google.com/p/lilypond/issues/detail?id=1670
I agree with Carl too.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
htt
Comment #3 on issue 1670 by percival.music.ca: Allow numbers in variable
names: violin1mvt2 = c'
http://code.google.com/p/lilypond/issues/detail?id=1670
I agree with Carl. I'm glad that Keith looked into it and clarified the
issue, but given the choices he laid out, I think the status quo
Comment #2 on issue 1670 by carl.d.s...@gmail.com: Allow numbers in
variable names: violin1mvt2 = c'
http://code.google.com/p/lilypond/issues/detail?id=1670
Personally, I prefer the current behavior. violinOne is no harder than
violin1 to read or type, and it keeps the syntax cleaner.
Li
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Postponed
New issue 1670 by k-ohara5...@oco.net: Allow numbers in variable names:
violin1mvt2 = c'
http://code.google.com/p/lilypond/issues/detail?id=1670
Users often request variable names including numbers or underscores
(http:/
18 matches
Mail list logo
