Mats Bengtsson ee.kth.se> writes:
>
> I hope that you also have tried
> http://lists.gnu.org/archive/html/lilypond-user/2005-03/msg00035.html
That helps in the case where all the rests are staff-wide.
I'll guess an example says more than words:
\version "2.9.19"
\score {
\context Staff {
I hope that you also have tried
http://lists.gnu.org/archive/html/lilypond-user/2005-03/msg00035.html
/Mats
Arvid Grøtting wrote:
Mats Bengtsson ee.kth.se> writes:
This is why many people try to use \partcombine for choral scores.
However, as you can see from the mailing list archives,
Mats Bengtsson ee.kth.se> writes:
> This is why many people try to use \partcombine for choral scores.
> However, as you can see from the mailing list archives, there are
> some problems with the current implementation of \partcombine.
Indeed there are. Partcombine may be useful for hymns -- I
Quoting Arvid Grøtting <[EMAIL PROTECTED]>:
Graham Percival gmail.com> writes:
I'm working on a viola trio right now, and these warning messages
completely conceal any other info. I shudder to think of all the
messages if I were doing an orchestral score.
I'm typesetting some TTBB choral m
Graham Percival gmail.com> writes:
> I'm working on a viola trio right now, and these warning messages
> completely conceal any other info. I shudder to think of all the
> messages if I were doing an orchestral score.
I'm typesetting some TTBB choral music now (as always), and I get
similar
Erik Sandberg schreef:
On Wednesday 04 October 2006 10:33, Han-Wen Nienhuys wrote:
Mats Bengtsson schreef:
really
well-defined which one and the program should definitely tell that that
the user probably has made a mistake and the program had to make a
decision on which mark to typeset.
In you
On Wednesday 04 October 2006 10:33, Han-Wen Nienhuys wrote:
> Mats Bengtsson schreef:
> > really
> > well-defined which one and the program should definitely tell that that
> > the user probably has made a mistake and the program had to make a
> > decision on which mark to typeset.
> >
> > In your
Han-Wen Nienhuys wrote:
Mats Bengtsson schreef:
really
well-defined which one and the program should definitely tell that
that the
user probably has made a mistake and the program had to make a decision
on which mark to typeset.
IMO, this is pretty well defined:
global = { s1*8 \mark \defau
Mats Bengtsson schreef:
really
well-defined which one and the program should definitely tell that that the
user probably has made a mistake and the program had to make a decision
on which mark to typeset.
In your case, you know why the warning appears and you know that you can
ignore it, since y
>
Cc:
Sent: Wednesday, October 04, 2006 5:05 PM
Subject: Re: Using \global - Lilypond 2.9.20 Windows
|I actually find the warning message relevant. Consider the following
| example:
| \score{
| <<
| \new Staff{ \mark "Mark in first stave" c'1}
| \new Staff{ \mark "Ma
I actually find the warning message relevant. Consider the following
example:
\score{
<<
\new Staff{ \mark "Mark in first stave" c'1}
\new Staff{ \mark "Mark in second stave" e'1}
>>
}
Clearly, LilyPond will only typeset one of these marks, but it's not
really
well-defined which one and the
Hi Everyone,
This seems to be a cosmetic problem but when using a global variable for
text marks or \newSpacingSection a warning: Two similatneous (whatver)
events, junking this one. The output is correct but the warnings never
appeared before.
Trent
===
C:\Documents an
12 matches
Mail list logo
