bug-lilypond  

Messages by Thread

• • Re: Collisions on OttavaBracket in the SVG output (BUG) Paolo Prete
• bug-reporting instructions need clarification Jace Toronto via bug-lilypond
  • Re: bug-reporting instructions need clarification David Kastrup
  • Re: bug-reporting instructions need clarification Jace Toronto via bug-lilypond
  • Re: bug-reporting instructions need clarification Jace Toronto via bug-lilypond
  • Re: bug-reporting instructions need clarification Werner LEMBERG
  • Re: bug-reporting instructions need clarification Jean Abou Samra
• Important request, participation in software development study ivandarioarroyo
  • RE:Important request, participation in software development study ivandarioarroyo
• layout doesn't work as I expected fcorvi
  • Re: layout doesn't work as I expected pkx166h
  • Re: layout doesn't work as I expected Francesco Corvi
• ly:page-turn-breaking core dumps Pierre-Luc Gauthier
  • Re: ly:page-turn-breaking core dumps Thomas Morley
  • Re: ly:page-turn-breaking core dumps Pierre-Luc Gauthier
  • Re: ly:page-turn-breaking core dumps David Kastrup
  • Re: ly:page-turn-breaking core dumps Pierre-Luc Gauthier
  • Re: ly:page-turn-breaking core dumps David Kastrup
  • Re: ly:page-turn-breaking core dumps Pierre-Luc Gauthier
• musicxml2ly does not honour the --nrp --no-rest-positions option jostle via LilyPond Bug Reports
• Re: french beaming incorrectly makes stems longer pkx166h
• Beams over rests and concaveness Gilberto Agostinho
• Can I help porting to python 3? Arusekk
  • Re: Can I help porting to python 3? Gwyn Ciesla via bug-lilypond
  • Re: Can I help porting to python 3? Karlin High
  • Re: Can I help porting to python 3? Jonas Hahnfeld via bug-lilypond
• \path markup command computes incorrect extents when using rmoveto after closepath Aaron Hill
  • Re: \path markup command computes incorrect extents when using rmoveto after closepath Aaron Hill
  • Re: \path markup command computes incorrect extents when using rmoveto after closepath Pierre Perol-Schneider
• compile message: programming error: no broken bound Martin Castillo
  • Re: compile message: programming error: no broken bound Martin Castillo
• accidentals after mid-measure break Malte Meyn
  • Re: accidentals after mid-measure break Peter Toye
  • Re: accidentals after mid-measure break David Kastrup
• Documentation suggestions. Peter Toye
  • Re: Documentation suggestions. Thomas Morley
  • Re: Documentation suggestions. Peter Toye
  • Re: Documentation suggestions. David Kastrup
  • Re: Documentation suggestions. Peter Toye
  • Re: Documentation suggestions. Carl Sorensen
  • Re: Documentation suggestions. Peter Toye
  • Re: Documentation suggestions. Trevor
  • Re: Documentation suggestions. Peter Toye
  • Re: Documentation suggestions. Peter Toye
• regression: assertion lilypond
  • Re: regression: assertion pkx166h
• Strange "programming error: Loose column ..." Thomas Morley
  • Re: Strange "programming error: Loose column ..." Malte Meyn
• MacOS 64bit support Yassine Chbani
  • Re: MacOS 64bit support pkx166h
• Lilypond & macOS B.M. van t Veer via bug-lilypond
  • Re: Lilypond & macOS Hans Åberg
• Unable to generate output David Honour
  • Re: Unable to generate output pkx166h
  • Re: Unable to generate output apricotfm
• top-markup-spacing does not work with markuplist Peter Toye
• LSR Snippet 318 Malte Meyn
• Midi block gives errors with bar number checks Peter Toye
  • Re: Midi block gives errors with bar number checks Carl Sorensen
  • Re: Midi block gives errors with bar number checks Peter Toye
  • Re: Midi block gives errors with bar number checks Peter Toye
  • Re: Midi block gives errors with bar number checks Carl Sorensen
  • Re: Midi block gives errors with bar number checks Peter Toye
  • Re: Midi block gives errors with bar number checks Martin Tarenskeen
  • Re: Midi block gives errors with bar number checks Nikolai Hedler
• Errors with midi2ly and musicxml2ly Артем Тартаковский
  • Re: Errors with midi2ly and musicxml2ly Aaron Hill
  • Re: Errors with midi2ly and musicxml2ly Aaron Hill
  • Re: Errors with midi2ly and musicxml2ly m.tarensk...@zonnet.nl
  • Re: Errors with midi2ly and musicxml2ly Aaron Hill
  • Re: Errors with midi2ly and musicxml2ly Aaron Hill
  • Re: Errors with midi2ly and musicxml2ly Aaron Hill
  • Re: Errors with midi2ly and musicxml2ly Noeck
• bad documentation of ly:intlog2 Jaap de Wolff
• slurring grace to chord: collision Malte Meyn
  • Re: slurring grace to chord: collision Palmer Ralph
• Grace notes cause wrong Hairpin.to-barline behaviour Rutger Hofman
  • Re: Grace notes cause wrong Hairpin.to-barline behaviour Thomas Morley
• Changes for 2.19/2.20 should mention \afterGrace’s optional argument Malte Meyn
  • Re: Changes for 2.19/2.20 should mention \afterGrace’s optional argument James
• Tuplet numbers are not regularly aligned Pierre Perol-Schneider
  • Re: Tuplet numbers are not regularly aligned Palmer Ralph
• Sourcefoge search doesn't seem to work Peter Toye
  • Re: Sourcefoge search doesn't seem to work Trevor
  • Re: Sourcefoge search doesn't seem to work Aaron Hill
  • Re: Sourcefoge search doesn't seem to work Peter Toye
• Hairpin end misplaced Peter Toye
• Regression: 2.19.61 doesn't handle melisma properly with multiple voices Marnen Laibow-Koser
  • Re: Regression: 2.19.61 doesn't handle melisma properly with multiple voices Marnen Laibow-Koser
• Entering and leaving polyphony with lyrics behaving oddly Jacob Page
  • Re: Entering and leaving polyphony with lyrics behaving oddly Thomas Morley
• NR 5.5.6 Unpure-pure containers Graham King
• Clef change and measure length foxfanfare
  • Re: Clef change and measure length Malte Meyn
  • Re: Clef change and measure length foxfanfare
  • Re: Clef change and measure length Malte Meyn
  • Re: Clef change and measure length foxfanfare
  • Re: Clef change and measure length Thomas Morley
• Re: polyphony and TabStaff: don’t put two voices on the same string (Malte Meyn) Christopher Heckman
  • Re: polyphony and TabStaff: don’t put two voices on the same string (Malte Meyn) Malte Meyn
• Regression bug: Assertion error in 2.19.83 Mats Bengtsson
  • Re: Regression bug: Assertion error in 2.19.83 Mats Bengtsson
  • Re: Regression bug: Assertion error in 2.19.83 Malte Meyn
• polyphony and TabStaff: don’t put two voices on the same string Malte Meyn
• set-global-staff-size rejects set-global-fonts settings CieMaKat .
  • Re: set-global-staff-size rejects set-global-fonts settings Malte Meyn
  • Re: set-global-staff-size rejects set-global-fonts settings Malte Meyn
• \instrumentSwitch adds the name twice in contexts with multiple voices Chris J. M.
  • Re: \instrumentSwitch adds the name twice in contexts with multiple voices Thomas Morley
• Rests with stem tremolo cause LilyPond to fail silently Trevor Bača
  • Re: Rests with stem tremolo cause LilyPond to fail silently Malte Meyn
• Core dump: page-breaking.cc (line 1180) with \autoPageBreaksOff [2.19.83] Trevor Bača
• getting score information jaap de wolff
  • Re: getting score information Knute Snortum
• Accidentals misalignment depending upon ledger line numbers Pierre Perol-Schneider
  • Re: Accidentals misalignment depending upon ledger line numbers Noeck
  • Re: Accidentals misalignment depending upon ledger line numbers Pierre Perol-Schneider
• DynamicText artificially extends bar size when within a StaffGroup Jean-Baptiste Mazon
  • Re: DynamicText artificially extends bar size when within a StaffGroup Jean-Baptiste Mazon
  • Re: DynamicText artificially extends bar size when within a StaffGroup David Kastrup
  • Re: DynamicText artificially extends bar size when within a StaffGroup Jean-Baptiste Mazon
  • Re: DynamicText artificially extends bar size when within a StaffGroup Jean-Baptiste Mazon
• grob::rhythmic-location and \set Score.currentBarNumber Urs Liska
  • Re: grob::rhythmic-location and \set Score.currentBarNumber David Kastrup
  • Re: grob::rhythmic-location and \set Score.currentBarNumber Urs Liska
  • Re: grob::rhythmic-location and \set Score.currentBarNumber David Kastrup
  • Re: grob::rhythmic-location and \set Score.currentBarNumber Urs Liska
  • Re: grob::rhythmic-location and \set Score.currentBarNumber Davide Liessi
  • Re: grob::rhythmic-location and \set Score.currentBarNumber David Kastrup
  • Re: grob::rhythmic-location and \set Score.currentBarNumber Urs Liska
  • Re: grob::rhythmic-location and \set Score.currentBarNumber Davide Liessi
  • Re: grob::rhythmic-location and \set Score.currentBarNumber David Kastrup
• \balloonText applied to single note errors with symbol->string ?? Thomas Morley
  • Re: \balloonText applied to single note errors with symbol->string ?? David Kastrup
  • Re: \balloonText applied to single note errors with symbol->string ?? Thomas Morley
  • Re: \balloonText applied to single note errors with symbol->string ?? David Kastrup
• \tripletFeel and \partial Malte Meyn
  • Re: \tripletFeel and \partial Malte Meyn
• Update on 2965: mid-bar \newSpacingSection leads to collisions Simon Albrecht
• Stockhausen example on the website is missing Malte Meyn
  • Re: Stockhausen example on the website is missing Phil Holmes
  • Re: Stockhausen example on the website is missing Werner LEMBERG
  • Re: Stockhausen example on the website is missing Phil Holmes
  • Re: Stockhausen example on the website is missing Werner LEMBERG
  • Re: Stockhausen example on the website is missing Werner LEMBERG
  • Re: Stockhausen example on the website is missing Phil Holmes
  • Re: Stockhausen example on the website is missing Werner LEMBERG
  • Re: Stockhausen example on the website is missing Phil Holmes
  • Re: Stockhausen example on the website is missing Werner LEMBERG
• Non default tuplet error with 2.21 Andrew Bernard
  • Re: Non default tuplet error with 2.21 Thomas Morley
• Override Staff.StaffSymbol.color has no effect when first note is grace note Florian Grundig
  • Re: Override Staff.StaffSymbol.color has no effect when first note is grace note Malte Meyn
• LilyPond — Notation Reference: 2.9.4 Divisiones (v2.18/2.19) Pierre Perol-Schneider
  • Re: LilyPond — Notation Reference: 2.9.4 Divisiones (v2.18/2.19) Jean-Charles Malahieude
  • Re: LilyPond — Notation Reference: 2.9.4 Divisiones (v2.18/2.19) Jean-Charles Malahieude
  • Re: LilyPond — Notation Reference: 2.9.4 Divisiones (v2.18/2.19) Pierre Perol-Schneider
• Segfault with slur over tie 2.18.2 Jason Miller
  • Re: Segfault with slur over tie 2.18.2 Aaron Hill
  • Re: Segfault with slur over tie 2.18.2 Jason Miller
  • Re: Segfault with slur over tie 2.18.2 Aaron Hill
  • Re: Segfault with slur over tie 2.18.2 Jason Miller
• AccidentalSuggestion only for cautionary accidentals? Malte Meyn
  • Re: AccidentalSuggestion only for cautionary accidentals? Alexander Kobel
• Windows, melody_engraver, stem direction, last crashes report Pierre Perol-Schneider
• break-visibility of KeySignature and KeyCancellation inconsistent Malte Meyn
  • Re: break-visibility of KeySignature and KeyCancellation inconsistent Thomas Morley
• Re: bug-lilypond Digest, Vol 201, Issue 7 Anzick
• Error on Linux Anzick
  • Re: Error on Linux Malte Meyn
  • Re: Error on Linux Aaron Hill
  • Re: Error on Linux t.sefzick
  • Re: Error on Linux Anzick
  • Re: Error on Linux Werner LEMBERG
• Bug Report: fingering collide with phrasing slure Ruth Mersmann
  • Re: Bug Report: fingering collide with phrasing slure Malte Meyn
  • Re: Bug Report: fingering collide with phrasing slure Urs Liska
  • Re: Bug Report: fingering collide with phrasing slure Palmer Ralph
• Python 3 Gwyn Ciesla via bug-lilypond
  • Re: Python 3 Knut Petersen
  • Re: Python 3 Karlin High
  • Re: Python 3 Gwyn Ciesla via bug-lilypond
  • Re: Python 3 Knut Petersen
  • Re: Python 3 Frédéric
  • Re: Python 3 Frédéric
  • Python 3 Gwyn Ciesla via bug-lilypond
  • Re: Python 3 Werner LEMBERG
• Compilation error, due to changes in pango t.sefzick
  • Re: Compilation error, due to changes in pango Rafael Fontenelle
  • Re: Compilation error, due to changes in pango Simon Albrecht
  • Re: Compilation error, due to changes in pango foxfanfare
  • Re: Compilation error, due to changes in pango Werner LEMBERG
  • Re: Compilation error, due to changes in pango foxfanfare
  • Re: Compilation error, due to changes in pango haawda
  • Re: Compilation error, due to changes in pango Werner LEMBERG
  • Re: Compilation error, due to changes in pango Masamichi Hosoda
  • Re: Compilation error, due to changes in pango foxfanfare
  • Re: Compilation error, due to changes in pango Werner LEMBERG
  • Re: Compilation error, due to changes in pango Knut Petersen
  • Re: Compilation error, due to changes in pango t.sefzick

• Earlier messages
• Later messages