Eluze writes:
> maybe this example makes more sense:
>
> lyr=\lyricsto A \new Lyrics \lyricmode { this is bad. }
> mus=\new Voice= A {a b c}
> << \mus \lyr >>
>
> this triggers an error
>
> writing mus =... (with a space before the equal sign) works as well as
> enclosing the assignment before in
the assignment before in braces:
lyr={...}
can we conclude that it's best (or simplest) to always put a space after the
variable name being assigned a value?
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/error-unknown-escaped-string-after-defining-a-variab
Eluze writes:
> David Kastrup wrote
>> A={c d e}
>> \addlyrics { this is bad }
>>
>> would be legitimate, so the assignment is not complete without looking
>> at the next token, and the next token is \A which is not defined.
>
> how then would you complete an assignment or hinder \addlyrics { t
is
bad } to be assigned to A?
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/error-unknown-escaped-string-after-defining-a-variable-tp157873p157958.html
Sent from the Bugs mailing list archive at Nabble.com.
___
bug-lilypo
Eluze writes:
> with
>
> \version "2.19.0"
> A={c d e}
> \A
>
> I get the message "error: unknown escaped string: `\A'"
>
> putting something substantial(?) like a markup or another definition after
> the definition the variable A can be used without brackets:
>
> \version "2.19.0"
> A={c d e}
>
{c d e}
A={c d e}
\A
is this a bug, remediable?
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/error-unknown-escaped-string-after-defining-a-variable-tp157873.html
Sent from the Bugs mailing list archive at Nabble.com.
___
bug
