[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: "No tremolo to end"
From: |
Daniel Rosen |
Subject: |
RE: "No tremolo to end" |
Date: |
Tue, 31 Dec 2013 06:30:10 +0000 |
> -----Original Message-----
> From: Keith OHara [mailto:address@hidden
> Sent: Monday, December 30, 2013 11:03 PM
> To: address@hidden; Daniel Rosen
> Subject: Re: "No tremolo to end"
>
> > Keith, would you be willing to help me debug this? The project is
> > hosted in a Git repository on Bitbucket that I can link you to; I'm
> > not ready to share it with the whole list just yet. :-)
>
> Warning messages are there only to help find problems, often flagging
> ambiguous situations or situations where the program is known to do a bad
> job. If you checked and found no problems, don't worry about it.
>
> There was a similar unhelpful warning with tuplets in \partcombine, and now
> that I look at it (http://code.google.com/p/lilypond/issues/detail?id=245) the
> warning came whether there were unisons or not. We recently looked into it
> and decided to shut of the warning. What you describes sounds similar.
I see your point, but I subscribe to the school of thought that if there are no
problems with the file, then it should compile error-free.
If it really is a bug, then I'd like to report it as such, but I can't figure
out how to isolate it in a tiny example; this is where I'm requesting
assistance.
DR