On Monday 31 May 2004 17.32, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > I can imagine that there could be a quick & dirty fix for this particular
> > problem (check if lyricsto happened to add an extra bar, and if it did,
> > remove it). If this isn't going to be done, then I'd conside
[EMAIL PROTECTED] writes:
> I can imagine that there could be a quick & dirty fix for this particular
> problem (check if lyricsto happened to add an extra bar, and if it did,
> remove it). If this isn't going to be done, then I'd consider this bug either
> a wontfix or future bug, if you don't
On Monday 31 May 2004 15.18, Han-Wen Nienhuys wrote:
ior. It's not justified by this "bug".
>
> > And if it should be added, why isn't it added if you remove the
> > second staff?
>
> Because of the way \lyricsto works. The iterator for \lyricsto never
> determines when interpreting should stop. Th
[EMAIL PROTECTED] writes:
> On Monday 31 May 2004 12.55, Han-Wen Nienhuys wrote:
> > \header { texidoc =
> > "The upper staff is extended with an empty bar.
> >
> > The score is weird in the sense that the Lyrics context is
> > created within a Staff context. But if this is not allo
On Monday 31 May 2004 12.55, Han-Wen Nienhuys wrote:
> \header { texidoc =
> "The upper staff is extended with an empty bar.
>
> The score is weird in the sense that the Lyrics context is
> created within a Staff context. But if this is not allowed, then
> it should gi
\header { texidoc =
"The upper staff is extended with an empty bar.
The score is weird in the sense that the Lyrics context is
created within a Staff context. But if this is not allowed, then
it should give either a warning or an error."
}
I don't
