Issue 246 in lilypond: collision stanza number and system start

Issue 246: collision stanza number and system start http://code.google.com/p/lilypond/issues/detail?id=246 Comment #6 by gpermus: Docs updated. Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or beca

Issue 204 in lilypond: afterGrace eats up skip duration under strict-grace-spacing

Issue 204: afterGrace eats up skip duration under strict-grace-spacing http://code.google.com/p/lilypond/issues/detail?id=204 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed i

Issue 181 in lilypond: tremolo multiple voices with accidental(s) have bad position

Issue 181: tremolo multiple voices with accidental(s) have bad position http://code.google.com/p/lilypond/issues/detail?id=181 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed

Issue 181 in lilypond: tremolo multiple voices with accidental(s) have bad position

Issue 181: tremolo multiple voices with accidental(s) have bad position http://code.google.com/p/lilypond/issues/detail?id=181 Comment #2 by gpermus: Despite this being an "invalid" bug, it got fixed sometime before 2.11.34. :) Issue attribute updates: Status: Fixed -- You received

Issue 73 in lilypond: missing accidental reminder

Issue 73: missing accidental reminder http://code.google.com/p/lilypond/issues/detail?id=73 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this i

Issue 438 in lilypond: subdivideBeams sometimes fails

Issue 438: subdivideBeams sometimes fails http://code.google.com/p/lilypond/issues/detail?id=438 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of t

Issue 278 in lilypond: Segmentation fault from ragged-bottom

Issue 278: Segmentation fault from ragged-bottom http://code.google.com/p/lilypond/issues/detail?id=278 Comment #4 by gpermus: (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issu

Issue 201 in lilypond: octave-check treats , as '

Issue 201: octave-check treats , as ' http://code.google.com/p/lilypond/issues/detail?id=201 Comment #3 by gpermus: (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may

Issue 484 in lilypond: wrong kind of flat sign with makam

Issue 484: wrong kind of flat sign with makam http://code.google.com/p/lilypond/issues/detail?id=484 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields

Issue 483 in lilypond: staff-size should go in cut-&-paste section of lily-*.ly

Issue 483: staff-size should go in cut-&-paste section of lily-*.ly http://code.google.com/p/lilypond/issues/detail?id=483 Comment #2 by gpermus: Are you sure this made it into 2.11.34? I can't verify with 2.11.34-1 darwin-x86. Issue attribute updates: Status: Accepted -- You receive

Issue 182 in lilypond: convert-ly crashes on input from 1.4.1

Issue 182: convert-ly crashes on input from 1.4.1 http://code.google.com/p/lilypond/issues/detail?id=182 Comment #3 by gpermus: (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this iss

Issue 482 in lilypond: barline group changed in 2.11.33

Issue 482: barline group changed in 2.11.33 http://code.google.com/p/lilypond/issues/detail?id=482 Comment #5 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of

Issue 433 in lilypond: 2.11.30 segmentation fault

Issue 433: 2.11.30 segmentation fault http://code.google.com/p/lilypond/issues/detail?id=433 Comment #4 by gpermus: Trevor, could you test with 2.11.34? I can't verify this myself, since I don't have the input file. -- You received this message because you are listed in the owner or CC fiel

Issue 433 in lilypond: 2.11.30 segmentation fault

Issue 433: 2.11.30 segmentation fault http://code.google.com/p/lilypond/issues/detail?id=433 Comment #3 by gpermus: Trevor, could you test with 2.11.34? I can't verify this myself, since I don't have the input file. -- You received this message because you are listed in the owner or CC fiel

Re: Issue 391 in lilypond: using relative filepath in \include "foo.ly"

On 3 Oct 2007, at 22:27, [EMAIL PROTECTED] wrote: Issue 391: using relative filepath in \include "foo.ly" http://code.google.com/p/lilypond/issues/detail?id=391 A similar question showed up in the case of Bison for the use of skeleton files. There, it was decided that when the include is in

Issue 391 in lilypond: using relative filepath in \include "foo.ly"

Issue 391: using relative filepath in \include "foo.ly" http://code.google.com/p/lilypond/issues/detail?id=391 Comment #5 by mlewissmith: What do you mean about the nonstandard behaviour cf C preprocessor? From `info cpp': `#include "FILE"' This variant is used for header files of your ow

Re: odd beaming in tuplets

[EMAIL PROTECTED] wrote: [Sorry for doubles, but the image file wasnt included in the post sent from the web-interface. AV.] Hi there. Is the strange beaming inside the tuplet in the first 4/8 measure of this sniplet ex

Re: Lilypond does not allow space in filenames

Yes of course! Hmm, why didn't I think of that in the first place... On 3. okt. 2007, at 14.44, Hans Aberg wrote: I depends what you have put in your 'lilypond' script. I have put exec /Applications/LilyPond.app/Contents/Resources/bin/lilypond "$@" Then: $ lilypond "foo bar" GNU LilyPond

Re: Lilypond does not allow space in filenames

I depends what you have put in your 'lilypond' script. I have put exec /Applications/LilyPond.app/Contents/Resources/bin/lilypond "$@" Then: $ lilypond "foo bar" GNU LilyPond 2.11.33 warning: cannot find file: `foo bar' error: failed files: "foo bar" Hans Åberg On 3 Oct 2007, at 12

Re: Lilypond does not allow space in filenames

Hmmm, strange. I'm using MacOSX 10.4.10 (Intel). On 3. okt. 2007, at 12.29, Mats Bengtsson wrote: What operating system? It works like a charm in Windows and Linux. /Mats Quoting Erlend Aasland <[EMAIL PROTECTED]>: Lilypond does not allow spaces in filenames. Bug or feature? # lilypond "

Re: Lilypond does not allow space in filenames

What operating system? It works like a charm in Windows and Linux. /Mats Quoting Erlend Aasland <[EMAIL PROTECTED]>: Lilypond does not allow spaces in filenames. Bug or feature? # lilypond "1 - fl 1.ly" GNU LilyPond 2.11.34 warning: cannot find file: `1' Kind regards, Erlend Aasland _

Lilypond does not allow space in filenames

Lilypond does not allow spaces in filenames. Bug or feature? # lilypond "1 - fl 1.ly" GNU LilyPond 2.11.34 warning: cannot find file: `1' Kind regards, Erlend Aasland ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/