[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-user
Subject:    RE: "No tremolo to end"
From:       Daniel Rosen <drosen27 () gmail ! com>
Date:       2013-12-31 6:30:10
Message-ID: 16EC1EB64C3829458F85E80F7458FFD95EEDD563 () ENIGMA ! rosen ! lan
[Download RAW message or body]

> -----Original Message-----
> From: Keith OHara [mailto:k-ohara5a5a@oco.net]
> Sent: Monday, December 30, 2013 11:03 PM
> To: lilypond-user@gnu.org; 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


[prev in list] [next in list] [prev in thread] [next in thread]