> A git grep for beam-grouping returned only the snippet you referenced above.
>
> A git grep for "beam grouping" returned only one reference which was in the
> snippet you referenced above.
>
> Can you be more specific about where the doc references to
> beam-grouping are?
Sorry, for being imp
> "Carl" == Carl D Sorensen writes:
Carl> On 6/1/09 5:29 PM, "Peter Chubb"
Carl> wrote:
>>
>>
>> Hi,
>>
>> I've put up a page on how to get more realistic sounding MIDI
>> output from current LilyPond, along with the scripts and scheme
>> code used, at http://www.nicta.com.au/people/chub
On 6/1/09 5:29 PM, "Peter Chubb" wrote:
>
>
> Hi,
>
> I've put up a page on how to get more realistic sounding MIDI output
> from current LilyPond, along with the scripts and scheme code used, at
> http://www.nicta.com.au/people/chubbp/articulate
Peter,
I haven't had a chance to loo
Hi,
I've put up a page on how to get more realistic sounding MIDI output
from current LilyPond, along with the scripts and scheme code used, at
http://www.nicta.com.au/people/chubbp/articulate
It has before-and-after MIDI samples to listen to, and a full
description of what the script
On 6/1/09 5:16 AM, "Werner LEMBERG" wrote:
>
>
> In the docs there are references to both `beam-grouping' and
> `beat-grouping'. This is confusing. However, `beam-grouping' doesn't
> exist in the source code. I thus suggest to replace `beam-grouping'
> with `auto-beam beat-grouping' just
Currently, `to-barline' is set to ##f for trills. What about changing
it so that ##t is the default?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
In the docs there are references to both `beam-grouping' and
`beat-grouping'. This is confusing. However, `beam-grouping' doesn't
exist in the source code. I thus suggest to replace `beam-grouping'
with `auto-beam beat-grouping' just to avoid the term `beam-grouping'
altogether. The snippet `b
The lilypond grammar contains some extremely long lines which look
very bad in formatting (and are difficult to comprehend), for example
206 music_function_chord_body: music_function_identifier_musicless_prefix
EXPECT_MUSIC function_arglist_nonmusic
On Sun, May 31, 2009 at 09:20:24PM +0200, Jan Nieuwenhuizen wrote:
> diff --git a/gub/specs/darwin/odcctools.py b/gub/specs/darwin/odcctools.py
> index ee953c0..1d24944 100644
I'm getting very confused trying to figure out what file affects
the darwin-x86::cross/gcc compilations. Candidates are:
Joe Neeman writes:
[...]
>> p.s. Despite [As a result of?] banging my head against this
>> particular wall, I think I learned a little about Scheme +
>> Lilypond... that's some consolation! =)
>
> If it's any additional consolation, your approach would have been
> perfectly ok were it not for t
On Sun, May 31, 2009 at 09:20:24PM +0200, Jan Nieuwenhuizen wrote:
> diff --git a/gub/specs/darwin/odcctools.py b/gub/specs/darwin/odcctools.py
> index ee953c0..1d24944 100644
> --- a/gub/specs/darwin/odcctools.py
> +++ b/gub/specs/darwin/odcctools.py
> @@ -62,3 +62,8 @@ cd %(install_prefix)s%(cros
11 matches
Mail list logo