Re: chordmode :13 leaving out 11

Rune Zelder wrote: Manual says "thirds are added to the root until it reaches the specified number" which would be the correct thing to do. But when specifying :13, the 11 is left out, so that the chord name printed is "9/add13" instead of "13" And that's not all - if you enter ":13.11" to in

Issue 305 in lilypond: positioning of hairpins and dynamics

Issue 305: positioning of hairpins and dynamics http://code.google.com/p/lilypond/issues/detail?id=305 Comment #2 by lemzwerg: The hairpin should appear above the staff (due to the `^'). -- You received this message because you are listed in the owner or CC fields of this issue, or because you

Issue 335 in lilypond: extender passes beginning of second node

Issue 335: extender passes beginning of second node http://code.google.com/p/lilypond/issues/detail?id=335 Comment #2 by hanwenn: Duplicate of #331 Issue attribute updates: Status: Duplicate -- You received this message because you are listed in the owner or CC fields of this issue, or

Issue 331 in lilypond: Lyric extender extends far beyond end of voice

Issue 331: Lyric extender extends far beyond end of voice http://code.google.com/p/lilypond/issues/detail?id=331 Comment #4 by hanwenn: see also 335 -- 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 adjust y

Issue 404 in lilypond: request: setting the output filename

Issue 404: request: setting the output filename http://code.google.com/p/lilypond/issues/detail?id=404 Comment #1 by hanwenn: #(define output-suffix "bla") Will add -bla to the filename. The numbers will not be removed as it's to overwrite freshly generated output. I recommend writing a small

Issue 411 in lilypond: bar numbers too high in pianostaff

Issue 411: bar numbers too high in pianostaff http://code.google.com/p/lilypond/issues/detail?id=411 Comment #2 by hanwenn: Looks like a relic from the fixed-distance alignment / simplistic page layout time. Feel free to junk it. -- You received this message because you are listed in the own

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 #1 by hanwenn: Please detail cmd line options used, and provide a simple example file. -- You received this message because you are listed in the owner or CC fields of th

Issue 305 in lilypond: positioning of hairpins and dynamics

Issue 305: positioning of hairpins and dynamics http://code.google.com/p/lilypond/issues/detail?id=305 Comment #1 by hanwenn: I don't understand this image. What's the point? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred thi

Issue 335 in lilypond: extender passes beginning of second node

Issue 335: extender passes beginning of second node http://code.google.com/p/lilypond/issues/detail?id=335 Comment #1 by hanwenn: Hi, what's the use case for this? Normally there is a syllable under the 2nd note too. -- You received this message because you are listed in the owner or CC fie

Issue 380 in lilypond: cycling markup reference segfaults

Issue 380: cycling markup reference segfaults http://code.google.com/p/lilypond/issues/detail?id=380 Comment #4 by hanwenn: this won't work with mutual recursion, f1 = \markup \fromproperty #'header:f2 f2 = \markup \fromproperty #'header:f1 -- You received this message because you are l

Issue 389 in lilypond: \t -> tab in LSR snippets

Issue 389: \t -> tab in LSR snippets http://code.google.com/p/lilypond/issues/detail?id=389 Comment #1 by hanwenn: LilyPond will interpret \t in the input as tab. These need to be escaped when generating the texidoc strings. Issue attribute updates: Summary: \t -> tab in LSR snippets

Issue 393 in lilypond: Line-breaking causes one case of beam insanity

Issue 393: Line-breaking causes one case of beam insanity http://code.google.com/p/lilypond/issues/detail?id=393 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_30 -- You received this message because yo

Issue 406 in lilypond: Feathered beams do not work with knees

Issue 406: Feathered beams do not work with knees http://code.google.com/p/lilypond/issues/detail?id=406 Comment #1 by hanwenn: this works for me [EMAIL PROTECTED] lilypond]$ git describe release/2.11.29-1-34-g625ae79 Issue attribute updates: Status: Invalid -- You received this me

Issue 408 in lilypond: Melismata at end of line aren't aligned properly

Issue 408: Melismata at end of line aren't aligned properly http://code.google.com/p/lilypond/issues/detail?id=408 Comment #1 by hanwenn: this is not actually true; I suspect that the 1st line looks like this due to spacing tweaks. If you want lyrics to stay inside, you need #'keep-inside-line i

Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t

Issue 405: tupletBracket not printed despite #'bracket-visibility=##t http://code.google.com/p/lilypond/issues/detail?id=405 Comment #1 by hanwenn: there is a cutoff that prevents very short brackets from being printed. This is to prevent brackets being inverted, which looks silly. (the bracket i

Issue 407 in lilypond: tabStaff cannot handle \partcombine

Issue 407: tabStaff cannot handle \partcombine http://code.google.com/p/lilypond/issues/detail?id=407 Comment #1 by hanwenn: TabStaff creates TabVoice, try this \version "2.10.1" melodia = \partcombine { e4 g g g }{e4 e e e } << \new TabStaff << \new TabVoice = "one" s1 \new TabVoice

Issue 411 in lilypond: bar numbers too high in pianostaff

Issue 411: bar numbers too high in pianostaff http://code.google.com/p/lilypond/issues/detail?id=411 Comment #1 by joeneeman: This is caused by \override VerticalAxisGroup #'minimum-Y-extent = #'(-4 . 4) in the definition of PianoStaff in engraver-init.ly. Does anyone know why we have this and w

Hidden accidental of tied note still takes space in 2.11.19

%{ A hidden accidental of a tied note still takes space, as visible in attached PNG, measure 2. As if the accidental is transparent instead of absent. %} \version "2.11.29" \paper { ragged-right = ##t } \new Staff \relative c'' << { c2 cis~ | cis c~ | c r } \\ { c,8 d e d c d e d | c d e d c d e

Issue 410 in lilypond: tie too short when clef change at end of system

Issue 410: tie too short when clef change at end of system http://code.google.com/p/lilypond/issues/detail?id=410 Comment #2 by wbsoft: I think this is caused by certain clef-related behaviour. Clef changes at the end of a measure in one staff also take space in the other staff. -- You recei

Forbid_line_break_engraver again

Related to the somewhat confused discussions in Issue 343, I have updated both the examples in the manual to actually show what they are supposed to show (not only the second one). However, there seems to be some real bugs here as well. When I try the following example with version 2.10.25, I do

Todays git shows #399 again I think

Hi, I compiled todays git (git checkout origin/master; git pull) but it looks like bug 399 has been introduced again: clefs use too much space when switching staff. http://code.google.com/p/lilypond/issues/detail?id=399 can anyone verify? ;) Wilbert Berendsen -- http://www.wilbertberendsen.nl