Erik Sandberg wrote:
Citerar Han-Wen Nienhuys <[EMAIL PROTECTED]>:
Log message:
* python/convertrules.py (conv): warning on \tempo{}
* ly/performer-init.ly: set tempoWholesPerMinute.
* lily/parser.yy (output_def_body): disallow \tempo in \midi{}
Hi,
Citerar Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> Log message:
> * python/convertrules.py (conv): warning on \tempo{}
>
> * ly/performer-init.ly: set tempoWholesPerMinute.
>
> * lily/parser.yy (output_def_body): disallow \tempo in \midi{}
Hi,
Why can't \tempo in \mi
On Fri, 2006-07-21 at 11:44 +, Han-Wen Nienhuys wrote:
> CVSROOT: /cvsroot/lilypond
> Module name: lilypond
> Changes by: Han-Wen Nienhuys06/07/21 11:44:59
> Log message:
> * scm/output-lib.scm (grace-spacing::calc-shortest-duration): new
> function.
>
> *
On 30-Jun-05, at 3:22 AM, Han-Wen Nienhuys wrote:
Graham Percival wrote:
Is there an easy way to apply changes to both branches? I imagine
that
the doc fixes for the next few weeks would apply to 2.6 as well as
2.7.
IMO the easiest most robust way is to edit the 2.6.0 -> 2.7.0 patch by
ha
Graham Percival wrote:
On 29-Jun-05, at 1:03 AM, Han-Wen Nienhuys wrote:
Log message:
Branch lilypond_2_6
(MINOR_VERSION): go to 2.7.0
Already? I thought that we'd work on 2.6.x for a while before branching
2.7.
Experience shows that it is really hard to make changes not break
a
On 29-Jun-05, at 1:03 AM, Han-Wen Nienhuys wrote:
Log message:
Branch lilypond_2_6
(MINOR_VERSION): go to 2.7.0
Already? I thought that we'd work on 2.6.x for a while before branching
2.7.
Is there an easy way to apply changes to both branches? I imagine that
the doc fixes fo
[EMAIL PROTECTED] writes:
>
>
> On Thu, 28 Oct 2004, Han-Wen Nienhuys wrote:
>
> > \paper {
> > indent=10.0\mm
> > linewidth=150.0\mm
> > +raggedbottom = ##t
> > }
>
>
> Hmmh, raggedright goes into the \layout block, but raggedbottom goes into
> the \paper block. This is not
ED], Juergen Reuter <[EMAIL PROTECTED]>
Subject: Re: lilypond ./ChangeLog ./VERSION input/test/corio...
On Thu, 28 Oct 2004, Han-Wen Nienhuys wrote:
> \paper {
> indent=10.0\mm
> linewidth=150.0\mm
> +raggedbottom = ##t
> }
Hmmh, raggedright goes into th
[EMAIL PROTECTED] writes:
> Thanks also for implementing function kill-ambitus, but ...
> For a new lilypond user without knowledge of lilypond internals, I think
> it will be conceptually hard to understand why to transform the input by
> some magic function in order to compensate something that i
On Wed, 17 Sep 2003, Han-Wen Nienhuys wrote:
> Modified files:
> . : ChangeLog VERSION
> Documentation/user: refman.itely
> ...
> Added files:
> input/test : ambitus-mixed.ly
>
Thanks a lot for the shift-ambitus workaround!
Thanks also for implementing functi
10 matches
Mail list logo
