Re: Strange parsing of define output-suffix "AA"

[Reinhold Kainhofer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Dienstag, 30. Dezember 2008 11:41:13 schrieb Villum Sejersen:
> lilypond 2.12.0-1 - 2.11.65-1 and most likely older versions too
>
> The other day I tried to spare myself some post-file-renaming, (in the
> \global section in a rather simple 5-voice choral score) using:
>
>       #(define output-suffix "SAATB_d-major")
>
> To my surprise the resulting filenames became:
> MyMelodyName-S_TB_d-major, not the expected MyMelodyName-SAATB_d-major.

I can't reproduce this here with "GNU LilyPond 2.12.1"... Can you give a full 
(minimal) example, please?

The only place where AA comes into play in the source code is in 
lily/lexer.ll, where AA is a keyword for pattern matching:
    AA                {A}|_

But to track down a possible problem, we need a test case that reliably shows 
the problem...

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJWhcoTqjEwhXvPN0RAuluAJ9rZF50dV6HOzSFoi0Uh6vlTApg9wCgj1kk
GDUXEvoUvX+eVaMJNuqi0iU=
=8Kdv
-----END PGP SIGNATURE-----