Hi,
The attached patch cleans up music functions:
- functions can have any arity, and parameters can be mixed in any way.
- implementation: A music function generates a sequence of tokens, so e.g. a
(markup? music? scm?) function generates tokens MUSIC_FUNCTION EXPECT_SCM
EXPECT_MUSIC EXPECT_MAR
Hi,
gub seems to work fairly well now. However, there are some problems: make doc
fails on the following snippet, seems to be a GC problem. A portion of the
output is attached.
Also, the patches I applied yesterday (updating \midi {\tempo}) are needed to
finish make doc, but the autotester nev
Hi,
I think I have found a bug in musicxml2ly and I also have a fix for it.
BUG: musicxml2ly only outputs major key signatures, not minor (or other modes).
The problem is in the python code that reads the MusicXML file.
FIX: in musicxml.py, change line 168 from
mode_node = self.get_maybe_exi
On Thu, Aug 24, 2006 at 02:47:33PM +0200, Mats Bengtsson wrote:
I think the problem here was the general knowledge of how to set
properties, which certainly is described in the manual, but probably
not in the parts of the manual which you read the first time. In my
opinion, we cannot keep repeati
I finally managed to compile and use lilypond from cvs in Debian sid.Apparently, the problems were - mftrace 1.2.0 (compiled by me), which I updated to 1.2.4 (from debian sid), and - old fonts in old installations (it is not possible to make uninstall if version number was changed, however, this i
Phillip Kirlin wrote:
FIX: in musicxml.py, change line 168 from
mode_node = self.get_maybe_exist_named_child ('mode')
to
mode_node = key.get_maybe_exist_named_child ('mode')
This is my first bug fix; I've never contributed to the project before
(though I've been using Lilypond), so I hope I'
On 8/24/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Hmmm, I'm not sure this is a good idea. Although it checks each release
only once, it does run hourly, so this will generate a huge amount of
email. Perhaps it would be better to only send a message when the
status goes back from "failed"
Erik Sandberg wrote:
Hi,
Whenever the GUB autotester has failed and someone committed something
new, I only want to update to the new revision if it is not broken.
Would it be possible to add a brief "GUB autotester succeeded"
message, similar to the current failure notice, which the autotester
Hi,
Whenever the GUB autotester has failed and someone committed something
new, I only want to update to the new revision if it is not broken.
Would it be possible to add a brief "GUB autotester succeeded"
message, similar to the current failure notice, which the autotester
spits out whenever it
Graham Percival wrote:
Ted Walther wrote:
On Wed, Aug 23, 2006 at 08:50:31PM +0200, Mats Bengtsson wrote:
Just as any other property setting that applies to a certain Staff, you
have to do the setting within the Staff context, for example:
\new Staff {
\time 3/4
\key d \major
Han-Wen Nienhuys wrote:
I've added you as an admin, so you can alter the labels yourself.
Thanks. Everything else looks ok; I'll start working on this when I've
finished the remaining doc stuff.
- Graham
___
lilypond-devel mailing list
lilypond
11 matches
Mail list logo
