胡海鹏 - Hu Haipeng writes:
> Dear David,
> I just came back from Osaka, Japan. I just tried the latest build
> with modified mydefs.ly, and there are errors on #
> (define-music-function... at the second half of the file. But some
> such functions don't generate error. Why?
If you fixed the func
Dear David,
I just came back from Osaka, Japan. I just tried the latest build with
modified mydefs.ly, and there are errors on #(define-music-function... at the
second half of the file. But some such functions don't generate error. Why?
Regards
Haipeng
_
胡海鹏 - Hu Haipeng writes:
> Dear David,
> Thank you for the further patch. I can wait for the fix, but don't
> know what you mean my hiding of in mydefs.ly. This file was
> created mainly from many lilyponders' macros, and my ones are only
> text variables such as \rit, \allegro and some contex
Dear David,
Thank you for the further patch. I can wait for the fix, but don't know what
you mean my hiding of in mydefs.ly. This file was created mainly from
many lilyponders' macros, and my ones are only text variables such as \rit,
\allegro and some contexts.
Haipeng
_
David Kastrup writes:
> David Kastrup writes:
>
>> David Kastrup writes:
>>
>>> And then there is one thing that is quite non-obvious and needs fixing:
>>> a comment.
>>>
>>> % direction (either #UP or #DOWN)
>>>
>>> # and $ in comments inside of #{ ... #} are not completely
>>> unproblemat
David Kastrup writes:
> David Kastrup writes:
>
>> And then there is one thing that is quite non-obvious and needs fixing:
>> a comment.
>>
>> % direction (either #UP or #DOWN)
>>
>> # and $ in comments inside of #{ ... #} are not completely
>> unproblematic. $ was much more dangerous, now
David Kastrup writes:
> And then there is one thing that is quite non-obvious and needs fixing:
> a comment.
>
> % direction (either #UP or #DOWN)
>
> # and $ in comments inside of #{ ... #} are not completely
> unproblematic. $ was much more dangerous, now both $ and # are a bit
> more low-
胡海鹏 - Hu Haipeng writes:
> Hello,
> I modified some notes in my overture, and tried to recompile it. But
> Lilypond 2.15.20 suddenly aborted without any messages left in the
> log. It's at about bar 160, but I can't detect any error, because it
> compiled well when i use 2.13. I don't use anyth
Haipeng,
2011/12/6 胡海鹏 - Hu Haipeng
> Hello,
> I modified some notes in my overture, and tried to recompile it. But
> Lilypond 2.15.20 suddenly aborted without any messages left in the log.
> It's at about bar 160, but I can't detect any error, because it compiled
> well when i use 2.13. I don
Le Dec 6, 2011 à 4:37 AM, 胡海鹏 - Hu Haipeng a écrit :
> Hello,
> I modified some notes in my overture, and tried to recompile it. But
> Lilypond 2.15.20 suddenly aborted without any messages left in the log. It's
> at about bar 160, but I can't detect any error, because it compiled well when
>
10 matches
Mail list logo
