On 11/18/06, Trevor Bača [EMAIL PROTECTED] wrote:
Hi,
Unlike certain other programs, I've found that the warnings that Lily
issues during parsing, interpretation and preprocessing usually matter
a great deal; warnings are usually a sign either that there's a bug
that needs to be reported or that I'm doing something wrong that will
eventually come to haunt me.
For that reason I like to run completely 'clean' lilypond files that
generate no warnings whatsoever. And, in fact, this has always been
possible to do, even in very complex cases.
But now I've run into the following case:
%%% BEGIN %%%
\version 2.10.0
\new Staff
\new Voice \with {
\override Stem #'direction = #up
} { c''4 c''4 c''4 c''4 }
\new Voice \with {
\override Stem #'transparent = ##t
\override NoteHead #'duration-log = #1
} { e'4 e'4 e'4 e'4 }
\new Voice \with {
\override Stem #'direction = #down
} { c'4 c'4 c'4 c'4 }
%%% END %%%
GNU LilyPond 2.10.0
Processing `348.ly'
Parsing...
Interpreting music... [1]
Preprocessing graphical objects...
348.ly:6:27: warning: ignoring too many clashing note columns
} { c''4 c''4 c''4
c''4 }
348.ly:6:22: warning: ignoring too many clashing note columns
} { c''4 c''4
c''4 c''4 }
348.ly:6:17: warning: ignoring too many clashing note columns
} { c''4
c''4 c''4 c''4 }
348.ly:6:12: warning: ignoring too many clashing note columns
} {
c''4 c''4 c''4 c''4 }
Layout output to `348.ps'...
Converting to `348.pdf'...
The resulting output is letter-prefect (see ex), but there are copious
warnings. What's going on here is that I've concocted a special
notation that renders the middle notes of each 'chord' stemless with
Stem #'transparent = ##t (rather than, say, \remove Stem_engraver).
The Stems in the middle Voice still exist, though, so that clashing
note column warnings result.
So my question is: is there any way to turn off the clashing note
column warnings? I think this is the one place where one of Lily's
warnings truly is completely harmless and I feel safe turning it off.
More importantly, I really need to see any *other* warnings that Lily
generates, which is quite hard given the original sourcefile (which
runs many thousands of lines).
(I could of course pass Lily's output through sed, but that doesn't
seem as clean as a commandline option to disregard this specific
warning, for example.)
Alternatively, is there some way I can doctor up my example to avoid
the clashing note column warnings in the first place (which would
actually be preferrable)?
As of the 2.11 series, there is a new feature that can be turned on with
\override NoteColumn #'ignore-collision = ##t
in the Score context.
The example above then renders with no warnings.
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
