On Sun, Jan 16, 2011 at 07:04:02AM +0100, Werner LEMBERG wrote:
>
> while walking through the log file I see many warnings for lilypond
> input files. Some of them are part of the regression test,
IMO those should be moved into a separate directory, intended for
such warnings.
> What about addi
On Sat, Jan 15, 2011 at 05:09:51PM -0800, Keith OHara wrote:
> Dear docs editors,
> Patch attached.
> (I had to wrap long lines of .ly; tried to pick a consistent indentation.)
Doc policy is 2-space indents, and in the case where you're
wrapping a long line, indent the first "wrapped" line by 2 s
On Sun, Jan 16, 2011 at 09:46:42AM +, Graham Percival wrote:
> I know that you were working on an old file which doesn't follow
> this policy, but would you mind making the examples follow this?
Never mind; it's fine as it is.
Cheers,
- Graham
___
Hi Keith
I've pushed this patch, but isn't the immediately preceding text
misleading,
in that it says,
"The following example demonstrates the two ways these alists can be
modified. The first declaration updates one key-value individually,
and the second completely re-defines the property:"?
Graham Percival writes:
> On Sun, Jan 16, 2011 at 07:04:02AM +0100, Werner LEMBERG wrote:
>>
>> while walking through the log file I see many warnings for lilypond
>> input files. Some of them are part of the regression test,
>
> IMO those should be moved into a separate directory, intended for
>> I personally would like some functions to print output at the
>> relevant stage:
>> #(ly:warning_parser (_ "blah"))
>> #(ly:warning_translator (_ "blah"))
>> #(ly:warning_event_class (_ "blah"))
>> #(ly:warning_engraver (_ "blah"))
>> #(ly:warning_performer (_ "blah"))
>> #(ly:warnin
On Sun, Jan 16, 2011 at 10:55:55AM +0100, David Kastrup wrote:
> I'd rather we just use
> #(regtest:expext_warning (_ "Some particular warning"))
>
> before the line being the eventual cause of some expected warning, and
> ly:warning get hijacked, matching the expected warnings to the given
> warn
following up myself:
[ after complaining about my large scores ]
>> This seems to work (at least, the regtests are OK and it doesn't
>> appear to break the interaction between page-count and
>> systems-per-page):
> [...]
>> I don't know why, though. :)
>
> it works for me in the sense that there'
On Sun, Jan 16, 2011 at 06:43:35AM +0100, Werner LEMBERG wrote:
>
> During compilation of font-name-font-size.ly I get this message:
...
> I suggest, for the sake of a `complete' compilation which doesn't
> depend on even more external stuff, that these lines in the regression
> file
>
> "strin
>> It would be simplest if the test selects an Emmentaler font:
>>
>> "pfsm"
>> \override #'(font-name . "Emmentaler-20")
>> "pfsm"
>
> With this change, I see a dramatic change in font size -- the
> vertical length of the post-font-name "p" is less than half of the
> vertical length of the
On Sun, Jan 16, 2011 at 07:50:57PM +0100, Werner LEMBERG wrote:
> > With this change, I see a dramatic change in font size -- the
> > vertical length of the post-font-name "p" is less than half of the
> > vertical length of the pre-font-name "p".
>
> Yes. However, it doesn't matter IMHO. On the
On Sun, 2011-01-16 at 19:02 +, Graham Percival wrote:
> On Sun, Jan 16, 2011 at 07:50:57PM +0100, Werner LEMBERG wrote:
> > > With this change, I see a dramatic change in font size -- the
> > > vertical length of the post-font-name "p" is less than half of the
> > > vertical length of the pre-f
12 matches
Mail list logo
