Hi Han-wen,
I get a crash with the following crashdump running from the command
line. Hope that helps.
Josh
Process: lilypond [1248]
Path:/Applications/LilyPond.app/Contents/Resources/bin/
lilypond
Identifier: lilypond
Version: ??? (???)
Code Type: X
Hi,
thanks for the heads up. With a bit of patching, I got the SVN version
of these tools to build a darwin-x86 installer; I have no idea
whether it worked, though. Could people on x86 macos 10.5 check out
http://lilypond.org/~hanwen/lilypond-2.11.61-0.darwin-x86.tar.bz2
and report whether it
Hello,
This patch fixes `make all' and `make web'. Can someone apply it for
me? Thanks.
-Patrick
>From 0a71cddf46357085aab922b6041a532eefb0cfe3 Mon Sep 17 00:00:00 2001
From: Patrick McCarty <[EMAIL PROTECTED]>
Date: Sun, 28 Sep 2008 19:59:20 -0700
Subject: [PATCH] Fix compile
* complete the c
On Sun, Sep 28, 2008 at 9:52 AM, Valentin Villenave
<[EMAIL PROTECTED]> wrote:
> By the way, guitar/harp/piano/percussions are a same group in
> orchestras, whereas strings are another group. Besides, harp notation
> is (on a semantic/symbolic level) much closer to keyboards or guitar
> stuff than
Hello,
When I do `make check-xrefs' in Documentation/, I get this output at the end:
Checking cross-references...
*** Warning: this file is automatically generated, please fix the code
source instead of generated documentation.
*** Warning: this file is automatically generated, please fix the cod
I'm running the version from http://lilypond.org/web/install/#2.11
which is labeled "MacOS X (G3, G4, G5 Macs) 10.3 and newer" on 10.5.5
(the latest).
When I get time, I'll try to narrow it down to a specific version for
you.
--
Dan
On 28 Sep 2008, at 14:18, Valentin Villenave wrote:
2
2008/9/28 Dan Eble <[EMAIL PROTECTED]>:
> Here's the whole file for now. It's not that I mind narrowing down the
> problem for you; I just can't do it today. Let me know if you need a more
> restricted example.
when compiling the whole file, I get two 3/4 barchecks warnings, but
no 0/0. Strange.
2008/9/28 Dan Eble <[EMAIL PROTECTED]>:
> Here's the whole file for now. It's not that I mind narrowing down the
> problem for you; I just can't do it today. Let me know if you need a more
> restricted example.
> On 28 Sep 2008, at 13:09, Valentin Villenave wrote:
>> When I try only the sample y
Here's the whole file for now. It's not that I mind narrowing down
the problem for you; I just can't do it today. Let me know if you
need a more restricted example.
tr8_Les_Rameaux.ly
Description: Binary data
--
Dan
On 28 Sep 2008, at 13:09, Valentin Villenave wrote:
2008/9/28 Dan
2008/9/28 Dan Eble <[EMAIL PROTECTED]>:
> Obviously "4" instead of "r4" is a typo, but where does "0/0" come from?
When I try only the sample you gave, I've got a 3/4 barcheck error (not 0/0);
could you post a complete file (or at least one that reproduces the warning)?
Cheers,
Valentin
__
Just upgraded to 2.11.60 (from 57 maybe?), and got this unusual error.
src/transcriptions/tr8_Les_Rameaux.ly:29:64: warning: barcheck
failed at: 0/0
gf,4 f) bf~ \times 2/3 { bf8 c df } | ef4 r ef, r | af r af 4
Obviously "4" instead of "r4" is a typo, but where does "0/0" come from?
2008/9/28 Trevor Daniels <[EMAIL PROTECTED]>:
> OK, let's wait to hear from John and Valentin on this point.
Well, at first I was pleased with the fretted/unfretted distinction,
but you do have some good points.
As far as I can remember, when we created the unfretted section it was
mainly to add
Graham Percival wrote Sunday, September 28, 2008 11:48 AM
On Sun, 28 Sep 2008 11:35:36 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
I just got round to looking at Unfretted strings in the Notation
Reference, and I'm not very happy with this subdivision.
1. It makes a nice contrast wit
On 27.09.2008 (02:16), Juergen Reuter wrote:
>
>
> On Wed, 24 Sep 2008, =?ISO-8859-1?Q?Eyolf_=D8strem_ wrote:
>
> Originally, I borrowed the term "Episem" from the OpusTeX implementation of
> Gregorian Chant. Just a couple of minutes ago, I did a small search on
> Google and have to agree that t
On Sat, Sep 27, 2008 at 4:19 PM, Patrick McCarty <[EMAIL PROTECTED]> wrote:
>
> I can successfully compile odcctools on x86 with this patch using GCC
> 4.3.2.
I should note that I haven't tested this *with* GUB; I just succeeded
doing a standalone compile with --target=i686-apple-darwin8. I also
2008/9/28 Neil Puttock <[EMAIL PROTECTED]>:
> LGTM ;)
Yaaay! Applied and pushed; now _you_ will be the one to blame if
anything goes wrong :-)
> Just one minor issue: there's no description of the new style in the
> regtest's texidoc.
Indeed. Corrected.
Cheers,
Valentin
_
2008/9/28 Valentin Villenave <[EMAIL PROTECTED]>:
> Greetings,
>
> (I tried to use the online code-review thingy but I couldn't find a
> LilyPond repository there)
>
> this was a requested feature on our tracker, and the new accidentals
> architecture trom Rune now makes it easy to implement such f
On Sun, 28 Sep 2008 11:35:36 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> I just got round to looking at Unfretted strings in the Notation
> Reference, and I'm not very happy with this subdivision.
1. It makes a nice contrast with "fretted strings".
2. There's almost no content in that s
Greetings,
(I tried to use the online code-review thingy but I couldn't find a
LilyPond repository there)
this was a requested feature on our tracker, and the new accidentals
architecture trom Rune now makes it easy to implement such features.
Thank you for having a look at the attached patch.
I just got round to looking at Unfretted strings in the Notation
Reference, and I'm not very happy with this subdivision. At present
it includes bowed strings and plucked strings, which gives rise to
at least two problems. First, having two sub-divisions pushes the
real content down a level, wh
On Sun, 28 Sep 2008 09:26:14 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> Graham Percival wrote Sunday, September 28, 2008 1:55 AM
>
> > Trevor, please fix your text editor. :)
>
> Nowt to do wi' me, guv - I haven't touched NR 6.
Oops, sorry.
> As all these errors are within @example,
Graham Percival wrote Sunday, September 28, 2008 1:55 AM
Thanks! I'll also point out that since we (almost) always stick
lilypond code in complete examples, it's very obvious to see such
problems -- that's why @code{} should be used at a minimum.
Trevor, please fix your text editor. :)
No
22 matches
Mail list logo
