On Tue 13 Sep 2011, 16:51 Sietse Brouwer wrote:
>> When I add an empty set of lyrics to a voice with \addlyrics, the
>> compiler gives the following warning:
>> bug.ly:14:16: warning: cannot find Voice `vSoprano'
>> when in fact the problem is that the Lyrics expression is empty
On Tue, Sep 13, 20
Hello,
On Tue, Sep 13, 2011 at 3:51 PM, Sietse Brouwer wrote:
> Dear bug auditor,
>
> This bug concerns Lilypond 2.12.3. It may affect later versions, I
> have been unable to test this.
I don't get any errors on 2.15.11 - current unstable.
Attached a screenshot of the output
--
--
James
<>__
On Tue 13 Sep 2011, 16:51 Sietse Brouwer wrote:
> Dear bug auditor,
>
> This bug concerns Lilypond 2.12.3. It may affect later versions, I
> have been unable to test this.
> When I add an empty set of lyrics to a voice with \addlyrics, the
> compiler gives the following warning:
> bug.ly:14:16: wa
Dear bug auditor,
This bug concerns Lilypond 2.12.3. It may affect later versions, I
have been unable to test this.
When I add an empty set of lyrics to a voice with \addlyrics, the
compiler gives the following warning:
bug.ly:14:16: warning: cannot find Voice `vSoprano'
when in fact the problem i
On Tuesday 08 June 2004 00.54, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > [EMAIL PROTECTED] writes:
> > > Does this sound sensible?
> >
> > I'll think about it. The problem is that you have have to interpret
> > the music completely before you can decide whether or not to print an
> >
[EMAIL PROTECTED] writes:
> [EMAIL PROTECTED] writes:
> >
> > Does this sound sensible?
> >
>
> I'll think about it. The problem is that you have have to interpret
> the music completely before you can decide whether or not to print an
> error message. Hmm. Maybe I can put the error message in t
[EMAIL PROTECTED] writes:
>
> Does this sound sensible?
>
I'll think about it. The problem is that you have have to interpret
the music completely before you can decide whether or not to print an
error message. Hmm. Maybe I can put the error message in the destructor
of the \newlyrics iterator.
On Sunday 06 June 2004 23.58, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Throwing warnings can (and should?) be seen as a sign that you have done
> > something "the wrong way", i.e. that you are recommended to do it some
> > other way. But I think I've done my music the way that should
[EMAIL PROTECTED] writes:
> Throwing warnings can (and should?) be seen as a sign that you have done
> something "the wrong way", i.e. that you are recommended to do it some other
> way. But I think I've done my music the way that should be recommended.. at
> least I have found no good alternati
On Sunday 06 June 2004 23.23, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > Hi,
> >
> > I have a feeling that voice-warning might be considered pretty close to
> > not-a-bug right now. So I'd like to state that this is not the case:
> > There are sit
[EMAIL PROTECTED] writes:
> Hi,
>
> I have a feeling that voice-warning might be considered pretty close to
> not-a-bug right now. So I'd like to state that this is not the case: There
> are situations where the voice-warning bug is very annoying.
I've added a flag i
Hi,
I have a feeling that voice-warning might be considered pretty close to
not-a-bug right now. So I'd like to state that this is not the case: There
are situations where the voice-warning bug is very annoying.
I'm working on a vocal piece which is composed of a number of different
12 matches
Mail list logo