Issue 437 in lilypond: alignAboveContext doesn't work as expected

Issue 437: alignAboveContext doesn't work as expected http://code.google.com/p/lilypond/issues/detail?id=437 Comment #3 by lemzwerg: (No comment was entered for this change.) Issue attribute updates: Status: New -- You received this message because you are listed in the owner or CC fie

Issue 437 in lilypond: alignAboveContext doesn't work as expected

Issue 437: alignAboveContext doesn't work as expected http://code.google.com/p/lilypond/issues/detail?id=437 Comment #2 by lemzwerg: OK, I modify my request: what I want is that the skylining algorithm (or whatever) places the second alias down to the base system. With other words, I consider

Issue 629 in lilypond: input/regression/tie-accidental.ly

Issue 629: input/regression/tie-accidental.ly http://code.google.com/p/lilypond/issues/detail?id=629 Comment #2 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Labels: -Priority-Medium Priority-Regression -- You received this message because you are liste

Issue 437 in lilypond: alignAboveContext doesn't work as expected

Issue 437: alignAboveContext doesn't work as expected http://code.google.com/p/lilypond/issues/detail?id=437 Comment #1 by hanwenn: Unfortunately, this is not how it works. If you want to have them on the same height, you have to make sure the staff continues (and perhaps start/stop it \startS

Issue 435 in lilypond: degenerated broken ties in chords

Issue 435: degenerated broken ties in chords http://code.google.com/p/lilypond/issues/detail?id=435 Comment #1 by hanwenn: yuck - bumping prio Issue attribute updates: Labels: -Priority-Medium Priority-High -- You received this message because you are listed in the owner or CC fields o

Issue 448 in lilypond: KeyCancellation spacing issue when staves have different key signatures

Issue 448: KeyCancellation spacing issue when staves have different key signatures http://code.google.com/p/lilypond/issues/detail?id=448 Comment #3 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Labels: -Priority-Medium Priority-Low -- You received thi

Issue 439 in lilypond: script collides with cross-staff beam

Issue 439: script collides with cross-staff beam http://code.google.com/p/lilypond/issues/detail?id=439 Comment #2 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Labels: -Type-Defect Type-Collision -- You received this message because you are listed in t

Issue 502 in lilypond: hairpins bound to spacer notes are aligned on lyrics

Issue 502: hairpins bound to spacer notes are aligned on lyrics http://code.google.com/p/lilypond/issues/detail?id=502 Comment #2 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Labels: -Priority-Medium Priority-Postponed -- You received this message beca

Issue 413 in lilypond: PNG image is offset an therefore cropped a little

Issue 413: PNG image is offset an therefore cropped a little http://code.google.com/p/lilypond/issues/detail?id=413 Comment #5 by hanwenn: marking invalid, since we have no feedback Issue attribute updates: Status: Invalid -- You received this message because you are listed in the owne

Issue 324 in lilypond: tremolo divisi causes new \Staff context to appear

Issue 324: tremolo divisi causes new \Staff context to appear http://code.google.com/p/lilypond/issues/detail?id=324 Comment #2 by hanwenn: actually, upon closer look: it's the fault of the \relative . It functions similar to << >> which at times also requires explicit \new. -- You received

Issue 324 in lilypond: tremolo divisi causes new \Staff context to appear

Issue 324: tremolo divisi causes new \Staff context to appear http://code.google.com/p/lilypond/issues/detail?id=324 Comment #1 by hanwenn: old problem- can't start a piece with << >> without explicit \context or \new. Issue attribute updates: Status: Invalid -- You received this mes

Issue 313 in lilypond: missing warning for flat in changed font

Issue 313: missing warning for flat in changed font http://code.google.com/p/lilypond/issues/detail?id=313 Comment #4 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed -- You received this message because you are listed in the owner or CC fiel

Issue 624 in lilypond: Regression: wrong trill script horizontal alignement when using pitchedTrill

Issue 624: Regression: wrong trill script horizontal alignement when using pitchedTrill http://code.google.com/p/lilypond/issues/detail?id=624 Comment #1 by hanwenn: Joe can you look at this? Between these versions, we have commit 7e046d57b65afa3c1f923344c6b36cedbb76714b Author: Joe Neeman <

Re: Problems setting circle-padding

Am Dienstag, 10. Juni 2008 schrieb Steven Weber: > #(define-markup-command (myCircle layout props name) (string?) >   "Print the name inside a circle.  Syntax:  \\myCircle #\"note\"" >       (interpret-markup layout props > (markup #:line (#:override (circle-padding . 0.5) (#:circle

Re: Problems setting circle-padding

2008/6/9 Steven Weber <[EMAIL PROTECTED]>: > Any clue what's going on here, or why the exact string Lilypond claims to be > using internally doesn't work? You're missing a quote which stops guile from trying to evaluate it as a variable (it's a symbol): #(define-markup-command (myCircle layout p

RE: Problems setting circle-padding

Sure enough, that solved the problem! However, now I'm hitting a new issue. I'm trying to make a markup command that circles a string. I started by seeing what Lilypond generates: { \displayMusic { c'1 ^\markup { \override #'(circle-padding . 0.5) \circle "Hi" } } } Then copied that string to m

Re: Problems setting circle-padding

Hi Steven, 2008/6/9 Steven Weber <[EMAIL PROTECTED]>: > warning: cannot find property type-check for `circle-padding' (backend-type?). > perhaps a typing error? > warning: doing assignment anyway Circle-padding is a markup property only, so it's not designed for use as an override with TextScrip

Problems setting circle-padding

Lilypond version 2.11.48, Windows XP \version "2.11.48" { % This throws a warning, but pads the circle \override TextScript #'circle-padding = #0.5 c'1 ^\markup { \circle "Hi" } | % This causes a fatal error in lilypond (uncomment to