> Uh, at the moment, nothing is possible since no line of code has
> been written. If you are interested about what goes on in my head,
> you'd be able to use either \violin1 or \violin#1 naturally
\violin1 is OK for me. Regarding the calling syntax, I prefer to
define with
\set \violin1
an
On Fri, Dec 2, 2011 at 1:59 PM, David Kastrup wrote:
> I don't see why defmacro should have ceased working, so it might be
> worth revisiting the problems you experienced.
It's not defmacro that ceased working, it's just that I previously
used the old ly:make-music-function syntax, which you chan
Updates:
Labels: -Patch-new Patch-needs_work
Comment #1 on issue 2068 by gra...@percival-music.ca: Patch: Doc: CG: add
instructions for staging branch
http://code.google.com/p/lilypond/issues/detail?id=2068
(No comment was entered for this change.)
__
Comment #8 on issue 2067 by d...@gnu.org: Patch: Give \displayLilyMusic and
\displayMusic optional port arguments.
http://code.google.com/p/lilypond/issues/detail?id=2067
Uh, James? Could you double-check whether the message is introduced by
this particular patch?
__
Comment #1 on issue 2072 by d...@gnu.org: Add proper complex variables to
Lilypond
http://code.google.com/p/lilypond/issues/detail?id=2072
Well, I have to take back that particular syntax since it could not be made
to work: detecting assignment would require seeing the = as a lookahead
to
Werner LEMBERG writes:
>> I propose developing the infrastructure that allows saying
>> violin = \makeVector 2
>> and afterwards using
>> \violin 1 = { ... } % backslash is no typo here
>> as well as { ... \violin 1 }
>> It will be possible to use arbitrary numbers (or Scheme expressions)
>> as i
> I propose developing the infrastructure that allows saying
> violin = \makeVector 2
> and afterwards using
> \violin 1 = { ... } % backslash is no typo here
> as well as { ... \violin 1 }
> It will be possible to use arbitrary numbers (or Scheme expressions)
> as index, and this would straightfo
googlecode.com> writes:
> I propose developing the infrastructure that allows saying
> violin = \makeVector 2
> and afterwards using
> \violin 1 = { ... } % backslash is no typo here
> as well as { ... \violin 1 }
Remember that issue 1670 asked for numbers embedded in identifiers
violin1mvt2
Status: New
Owner: d...@gnu.org
Labels: Type-Enhancement Bounty
New issue 2072 by d...@gnu.org: Add proper complex variables to Lilypond
http://code.google.com/p/lilypond/issues/detail?id=2072
A frequent complaint on the mailing list is that Lilypond does not permit
identifiers with numbers in
Comment #5 on issue 2069 by carl.d.s...@gmail.com: Patch: More nuanced
BarLine extra-spacing-height to allow tighter horizontal spacing
http://code.google.com/p/lilypond/issues/detail?id=2069
To clarify my objection -- I don't like having the chord names so close
together. But I'm not oppo
"Mathias Weber" wrote in message
news:loom.20111203t113431-...@post.gmane.org...
In der deutschen Version der Seite:
http://lilypond.org/doc/v2.14/Documentation/learning/properties-found-
in-interfaces
Im Absatz
"Den Kontext im Liedtextmodus bestimmen" heißt es:
"Bei Gesangstexten funktioniert
Mathias Weber writes:
> Auf der deutschen Variante der Seite
>
> http://lilypond.org/doc/v2.14/Documentation/learning/contexts-explained
>
> heißt es im zweiten Absatz:
>
> "Während LilyPond den Eingabetext interpretiert, wird die musikalische
> Information von rechts nach links gelesen, in etwa,
Auf der deutschen Variante der Seite
http://lilypond.org/doc/v2.14/Documentation/learning/contexts-explained
heißt es im zweiten Absatz:
"Während LilyPond den Eingabetext interpretiert, wird die musikalische
Information von rechts nach links gelesen, in etwa, wie man eine Partitur von
links nach
Comment #4 on issue 2069 by mts...@gmail.com: Patch: More nuanced BarLine
extra-spacing-height to allow tighter horizontal spacing
http://code.google.com/p/lilypond/issues/detail?id=2069
Keith is right - if you transpose the example in snapshot.png up an octave,
you'll get the close spacing
In der deutschen Version der Seite:
http://lilypond.org/doc/v2.14/Documentation/learning/properties-found-
in-interfaces
Im Absatz
"Den Kontext im Liedtextmodus bestimmen" heißt es:
"Bei Gesangstexten funktioniert der \override-Befehl nicht mehr, wenn Sie den
Kontext im oben dargestellten Format
15 matches
Mail list logo
