"Bertalan Fodor (LilyPondTool)" writes:
> I thought it was part of 2.14.1 source tarballI, probably I have
> changed it myself accidentally, changed this line:
>
> $$ = scm_list_2 (ly_lily_module_constant ("line-markup"), $1);
> to
> $$ = $1;
>
> when playing with it, as the source tarballs ar
I thought it was part of 2.14.1 source tarballI, probably I have changed it
myself accidentally, changed this line:
$$ = scm_list_2 (ly_lily_module_constant ("line-markup"), $1);
to
$$ = $1;
when playing with it, as the source tarballs are correct.
Thank you for your help,
Bertalan
On Wed, Oct
"Bertalan Fodor (LilyPondTool)" writes:
> Thank you David, this explains me what I didn't understand.
> It turned out that somehow I was looking at a bad parser.yy.
Interesting. Where did you get it?
--
David Kastrup
___
lilypond-devel mailing li
Thank you David, this explains me what I didn't understand.
It turned out that somehow I was looking at a bad parser.yy.
Actually I'm not running/debugging the C code, but instead only reading it
(and porting some of the parsing code to Java).
Bertalan
On Wed, Oct 26, 2011 at 7:26 AM, David Kast
"Bertalan Fodor (LilyPondTool)" writes:
> Dear LilyPond devs,
>
> I have a problem with the LilyPond markup parsing, which prevents me
> to finish my new release of LilyPondTool.
> Could you help me a bit on that?
>
> I have this ly file
> --
> dot = \markup {
> "q" \musicglyph
Dear LilyPond devs,
I have a problem with the LilyPond markup parsing, which prevents me to
finish my new release of LilyPondTool.
Could you help me a bit on that?
I have this ly file
--
dot = \markup {
"q" \musicglyph #"accordion.dot"
}
{ c^\dot }
--
When the
