Aaron Hill writes:
> On 2022-05-24 7:40 am, Jean Abou Samra wrote:
>> Because there is now a command called \section, so this
>> is trying to set a key inside a music function, which is
>> not an alist ... This is unfortunate but unavoidable.
>
> Would it be practical for LilyPond to detect and w
Le 24/05/2022 à 18:06, Aaron Hill a écrit :
On 2022-05-24 7:40 am, Jean Abou Samra wrote:
Because there is now a command called \section, so this
is trying to set a key inside a music function, which is
not an alist ... This is unfortunate but unavoidable.
Would it be practical for LilyPond to
On 2022-05-24 7:40 am, Jean Abou Samra wrote:
Because there is now a command called \section, so this
is trying to set a key inside a music function, which is
not an alist ... This is unfortunate but unavoidable.
Would it be practical for LilyPond to detect and warn when a built-in is
being re
Le 24/05/2022 à 16:40, Jean Abou Samra a écrit :
this
is trying to set a key inside a music function
I have to correct myself. \section is defined as a music identifier, not
a music function.
The result is the same though.
___
bug-lilypond ma
Le 24/05/2022 à 16:37, Trevor Bača a écrit :
Hi,
The dot-chained variable names that became available in recent versions of
LilyPond are great, particularly because they allow numerals:
%%% EXAMPLE 1 %%%
\version "2.23.8"
movement.1.notes = { g'4 }
\new Staff { \movement.1.n
Hi,
The dot-chained variable names that became available in recent versions of
LilyPond are great, particularly because they allow numerals:
%%% EXAMPLE 1 %%%
\version "2.23.8"
movement.1.notes = { g'4 }
\new Staff { \movement.1.notes }
%%% END %%%
But LilyPond's parser er
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
Updates:
Status: Verified
Comment #17 on issue 1844 by philehol...@gmail.com: Changes variable names
in include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
Verified that the patch was pushed
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 variab
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:
&q
Updates:
Labels: -Patch-push fixed_2_15_14
Comment #16 on issue 1844 by tdaniels...@gmail.com: Changes variable names
in include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
(No comment was entered for this change
Updates:
Status: Fixed
Comment #15 on issue 1844 by mts...@gmail.com: Changes variable names in
include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
Fixed with e071fd8953f7391f206987c0b3dd3195f1727f1c
On Oct 19, 2011, at 4:03 AM, lilyp...@googlecode.com wrote:
>
> Comment #14 on issue 1844 by colinpkc...@gmail.com: Changes variable names in
> include/beam-scoring-problem.hh and beam-quanting.cc
> http://code.google.com/p/lilypond/issues/detail?id=1844
>
> Does this sti
Comment #14 on issue 1844 by colinpkc...@gmail.com: Changes variable names
in include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
Does this still need work, Mike? James had some concerns on Rietveld. The
patch has been on patch-push
Updates:
Labels: -Patch-countdown Patch-push
Comment #13 on issue 1844 by colinpkc...@gmail.com: Changes variable names
in include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
Counted down to 20111009
Updates:
Labels: -Patch-new Patch-review
Comment #11 on issue 1844 by pkx1...@gmail.com: Changes variable names in
include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
Passes make but I get a few reg tests show up. Attached
Updates:
Labels: Patch-new
Comment #10 on issue 1844 by mts...@gmail.com: Changes variable names in
include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844#c10
Sketch for broken beams with consistent slopes
http
Updates:
Labels: -Patch-countdown Patch-needs_work
Comment #9 on issue 1844 by pkx1...@gmail.com: Changes variable names in
include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
there is no Patch on-hold :) so I'll set this
Comment #8 on issue 1844 by colinpkc...@gmail.com: Changes variable names
in include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
Developer hjas asked specifically for feedback on beam-slope-stemlet.ly so
countdown is on hold
Updates:
Labels: -Patch-review Patch-countdown
Comment #7 on issue 1844 by colinpkc...@gmail.com: Changes variable names
in include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
(No comment was entered for this change
Updates:
Labels: -Patch-new Patch-review
Comment #6 on issue 1844 by pkx1...@gmail.com: Changes variable names in
include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
(No comment was entered for this change
Comment #5 on issue 1844 by pkx1...@gmail.com: Changes variable names in
include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
Passes make, a few reg tests that do need looking at
Attachments:
Screenshot.png 55.7 KB
Comment #4 on issue 1844 by percival.music.ca: Changes variable names in
include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
Issue 1923 has been merged into this issue.
___
bug-lilypond
Updates:
Labels: -Patch-needs_work Patch-new
Comment #3 on issue 1844 by percival.music.ca: Changes variable names in
include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
new version of patch
Updates:
Labels: -Patch-review Patch-needs_work
Comment #2 on issue 1844 by colinpkc...@gmail.com: Changes variable names
in include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
Mike plans changes to repair cross-staff beams
Updates:
Owner: mts...@gmail.com
Labels: -Patch-new Patch-review
Comment #1 on issue 1844 by pkx1...@gmail.com: Changes variable names in
include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
passes make and reg tests
Status: Accepted
Owner:
Labels: Type-Enhancement Patch-new
New issue 1844 by percival.music.ca: Changes variable names in
include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
http://codereview.appspot.com/4961041
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 wel
>> 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 charact
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 hav
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 t
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
> (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, y
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 nam
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
>
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 defini
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@gn
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
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 cl
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
Erik Sandberg writes:
>> not a bug; won't fix.
>
> ok, removed from cvs.
btw: is this documented?
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
___
bug-li
On Tuesday 17 August 2004 20.57, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Added this to cvs:
> >
> > %critical
> > %
> >
> > \header {texidoc = "Variable names can not be set to pitch names" }
> > \version "2.3.11"
[EMAIL PROTECTED] writes:
> Added this to cvs:
>
> %critical
> %
>
> \header {texidoc = "Variable names can not be set to pitch names" }
> \version "2.3.11"
>
> a = {c c c c}
not a bug; won't fix.
--
Han-Wen Nienhuys |
Added this to cvs:
%critical
%
\header {texidoc = "Variable names can not be set to pitch names" }
\version "2.3.11"
a = {c c c c}
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
46 matches
Mail list logo
