Issue 289 in project lilypond

Issue 289: grace note cancels \voiceOne http://code.google.com/p/lilypond/issues/detail?id=289 Comment #3 by arvidgr: Is #74 a regression since 2.11.5? If not, this can't possibly be a duplicate of that bug. Or at least it has grown a lot worse. Also, the workaround in #74 doesn't work anymore

Re: Text Spanners broken in 2.11.17

\override Glissando #'bound-details #'right #'text = \markup { \hcenter \bold down } ... which works for text spanners, too. Two overrides now instead of one (if you're wanting to override edge text at both the left and right of the spanner). But the upside is that padding and positioning of le

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #7 by horndude77: Same problem in 2.11.18. Perhaps it's been fixed since? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred th

Re: Rehearsal mark appears on wrong staff

Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=294 Cheers, - Graham Daniel Johnson wrote: Sorry, the previous example should have been: % BEGIN \version "2.11.17" spaceWide = { \overrideProperty #"Score.NonMusicalPaperColumn" #'line-break-system-details #'((ali

Issue 294 in project lilypond

Issue 294: absolute spacing moves Mark_engraver to wrong staff context http://code.google.com/p/lilypond/issues/detail?id=294 New issue report by gpermus: % multipage output, so no picture attached. %{ Daniel Johnson: When using absolute spacing and moving the Mark_engraver from the Score contex

Re: Path names including [space] character not accepted

It may be a bug in LilyPondTool. I hope it will be fixed in the next release (2.10.4, coming soon). Bert ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Path names including [space] character not accepted

lilpond v2.6.3 on ubuntu Edgy Eft. I created a folder "My Music" and moved my .ly files there. Then I started jEdit with the lilypond plugin, opened one of the files and let it process. Lilypond output reads as follows... It can be seen that the recognized path name stops at the [space] character,

Re: warning: Can't fit systems on page -- ignoring between-system-padding

On 2/13/07, Joe Neeman <[EMAIL PROTECTED]> wrote: On 2/12/07, Trevor Bača <[EMAIL PROTECTED]> wrote: > Hi, > > Pretty sure this is a bug, but thought I'd post to bug- first before > opening in Google. > > Sometimes I build .ly files that are essentially text docs as a > sequence of \markup comman

Issue 293 in project lilypond

Issue 293: warning: Can't fit systems on page -- ignoring between-system-padding http://code.google.com/p/lilypond/issues/detail?id=293 New issue report by trevorbaca: In versions up to the .11 dev series, what we might call "multipage markup" files would break onto multiple pages if there were en

Re: Rehearsal mark appears on wrong staff

Hi Graham, Definitely a bug. line-break-system-details shouldn't cause the mark to switch staves. Could you open in Google? Trevor. On 2/12/07, Graham Percival <[EMAIL PROTECTED]> wrote: Trevor, could you take a look at this? If I remove the spacing weirdness, the rehearsal mark is created o

Re: staff fails to wrap and runs off right hand side of pdf

LilyPond will only consider breaking a line at the bar lines and only if there isn't any note whose duration extends over the bar line. Since it's very common to make mistakes in the note durations, there's good support to find these mistakes, see "Bar check" in the manual. If you use Windows or M

staff fails to wrap and runs off right hand side of pdf

> I'm not top posting The pdf resulting from this is broken with the first (/partial 4) bar taking up the entire first line then nearly eight bars squeezed into the second line before running off the right hand side and the rest of the music not being visible. (The midi is fine.) I have made

ligature bracket affected by other voices

> I'm not top posting. The ligature bracket right-end is affected by other voices. In this example, the first ligature is printed correctly, but not the second because there is other voice doing quarters. --- \version "2.11.17" << \new Staff {\[b2 b\]

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #6 by joeneeman: Does it work in 2.11.18? It could be that the changes didn't make it in time for 2.11.17. It certainly looks OK when I run it with git head. Issue attribute updates: L

Re: warning: Can't fit systems on page -- ignoring between-system-padding

On 2/12/07, Trevor Bača <[EMAIL PROTECTED]> wrote: Hi, Pretty sure this is a bug, but thought I'd post to bug- first before opening in Google. Sometimes I build .ly files that are essentially text docs as a sequence of \markup commands. In versions up to the .11 dev series, what we might call

Issue 292 in project lilypond

Issue 292: ugly lyrics with ragged-bottom = ##f http://code.google.com/p/lilypond/issues/detail?id=292 New issue report by lemzwerg: \version "2.11.16" \header { texidoc = " Lyrics attached to a staff must have a sensible padding even if used with @[EMAIL PROTECTED] = ##f}}. The example bel

Issue 291 in project lilypond

Issue 291: \glissando doesn't work properly with chords http://code.google.com/p/lilypond/issues/detail?id=291 Comment #1 by lemzwerg: (No comment was entered for this change.) Issue attribute updates: Labels: -Priority-Regression Priority-Medium -- You received this message because yo

Issue 291 in project lilypond

Issue 291: \glissando doesn't work properly with chords http://code.google.com/p/lilypond/issues/detail?id=291 New issue report by lemzwerg: \version "2.11.16" \header { texidoc = " @code{\glissando} should be controllable for each note in a chord. The code below shows that only the uppermost