The MusicXML test file 71f-AllChordTypes (and other MusicXML files
also) produces zillions of this warning:
staff-affinities should only decrease
What does it mean? The output seems to be fine...
Werner
___
lilypond-devel mailing list
lilypon
Folks,
while walking through the log file I see many warnings for lilypond
input files. Some of them are part of the regression test, but some
not. An example for the former is, I think
In repeat-unfold.ly:
warning: More alternatives than repeats. Junking excess alternatives
and her a
During compilation of font-name-font-size.ly I get this message:
[century_schoolbook_l_serif_3.865234375]
[new_century_schoolbook_3.865234375]
warning: no PostScript font name for font
`/usr/share/fonts/100dpi/ncenR24-ISO8859-1.pcf.gz'
warning: FreeType face has no PostScript font name
James Worlton gmail.com> writes:
The following code compiles, but the spacing override in the layout block fails. The
layout block code was copied and pasted into my test directly from the NR 4.4.1
"Within-system spacing properties". ...
\override VerticalAxisGroup #'staff-staff-spacing #'b
On Sat, 15 Jan 2011 03:26:47 -0800, Keith OHara wrote:
On Fri, 14 Jan 2011 03:20:15 -0800, Joe Neeman wrote:
I think you'll find that the regression was caused by ee0488,
Yes. Reverting the commit to fix 1120, from current master :
[...]
+ and for some reason correctly spaces notes with me
Graham Percival writes:
> On Fri, Jan 14, 2011 at 09:58:15PM +, Neil Puttock wrote:
>> On 14 January 2011 21:04, David Kastrup wrote:
>>
>> > Sometimes I am inclined to just commit and be done. After all, this
>> > would just omit a warning in working cases, and would fix the totally
>> >
Another issue which is new since a few months, and which makes the log
file even more noisy: Some strings are printed twice, for no apparent
reason, e.g.
...
Parsing...
Using `nederlands' note names...
Using `nederlands' note names...
Renaming input to: `tie-direction-manual.ly'
...
On Fri, Jan 14, 2011 at 09:58:15PM +, Neil Puttock wrote:
> On 14 January 2011 21:04, David Kastrup wrote:
>
> > Sometimes I am inclined to just commit and be done. After all, this
> > would just omit a warning in working cases, and would fix the totally
> > broken warning message when breve
Saying `make doc' and diverting stdin and stderr to a file, I see
messages like this:
...
[/usr/local/home/wl/git/lilypond.compiled/out/share/lilypond/current/ly/predefined-fretboards-init.ly]
[/usr/local/home/wl/git/lilypond.compiled/out/share/lilypond/current/ly/string-tunings-init.ly
Usi
On 14 January 2011 20:56, Reinhold Kainhofer wrote:
>
> To be honest, I don't understand, why the Instrument_name_engraver is not
> added to all staff group contexts by default. It is a very simple engraver, so
> it would not induce much overhead. And it does not have any side effects. On
> the ot
2011/1/14 Carl Sorensen :
> On 1/13/11 2:16 PM, "Janek Warchoł"
> wrote:
>>
>> The distances are not equal. Optical corrections are made there.
>>
> OK, you got me interested so I spent some time I didn't have on this. I
> must be a LilyPond addict.
:)
I'm becoming one, too :)
> It appears that
2011/1/14 Reinhold Kainhofer :
> To be honest, I don't understand, why the Instrument_name_engraver is not
> added to all staff group contexts by default. It is a very simple engraver, so
> it would not induce much overhead.
> From a user's point of view, if he sets an instrument name, he wants it
12 matches
Mail list logo
