Archives are refreshed every 30 minutes - for details, please visit the main index.
You can also download the archives in mbox format.

bug-lilypond (date)

[Thread Index][Top][All Lists]

Advanced

[Prev Period]

Last Modified: Fri Jan 30 2009 15:20:38 -0500 Messages in reverse chronological order

[Next Period]

---

• January 30, 2009
  • Re: vista, Carl D. Sorensen, 15:20
  • Re: SeparationItem #'padding not working anymore?, Jonathan Kulp, 13:22
  • Re: SeparationItem #'padding not working anymore?, Graham Percival, 12:34
  • Re: SeparationItem #'padding not working anymore?, Graham Percival, 12:33
  • Re: SeparationItem #'padding not working anymore?, Carl D. Sorensen, 12:28
• January 29, 2009
  • Re: SeparationItem #'padding not working anymore?, Patrick McCarty, 15:58
  • Re: SeparationItem #'padding not working anymore?, Patrick McCarty, 15:36
  • Re: SeparationItem #'padding not working anymore?, Trevor Daniels, 12:28
  • SeparationItem #'padding not working anymore?, Mats Bengtsson, 10:31
• January 28, 2009
  • vista, Antoine Plante, 12:55
  • \time information is not being output to midi file, Marten Visser, 09:05
• January 26, 2009
  • Linebreak difference between 2.10.33 and 2.12.2, Andreas Scherer, 14:09
  • Issue 37 in lilypond: collision notehead and beams, codesite-noreply, 12:58
• January 24, 2009
  • Re: [frogs] Re: IR 3.2.111 doesn't mention 'numbered style, Patrick McCarty, 16:05
  • Re: IR 3.2.111 doesn't mention 'numbered style, Carl D. Sorensen, 14:23
  • IR 3.2.111 doesn't mention 'numbered style, Mark Polesky, 02:47
• January 22, 2009
  • Misleading warning message when \lyricmode block is empty, Chris Snyder, 16:57
• January 21, 2009
  • Issue 735 in lilypond: Lilypond 2.12 on OSX errors when trying to change a font., codesite-noreply, 12:22
  • Issue 735 in lilypond: Lilypond 2.12 on OSX errors when trying to change a font., codesite-noreply, 12:18
• January 20, 2009
  • Issue 376 in lilypond: tremolo beams can collide with notes, codesite-noreply, 18:32
  • Issue 734 in lilypond: tremolos beams placement on a (single) whole note, codesite-noreply, 17:33
  • Issue 735 in lilypond: Lilypond 2.12 on OSX errors when trying to change a font., codesite-noreply, 17:14
  • about Liypond, Roi Redondo Garcia, 16:45
• January 19, 2009
  • When gregorian.ly is included, SpacingSpanner does not work., Jiri Zurek, 15:52
• January 17, 2009
  • Whole note tremolo outside staff, Lasse, 06:55
• January 16, 2009
  • Re: make web segfaults with 967b27d, Jan Nieuwenhuizen, 13:05
  • Re: make web segfaults with 967b27d, Joe Neeman, 12:58
  • make web segfaults with 967b27d, Jan Nieuwenhuizen, 09:57
• January 14, 2009
  • Issue 441 in lilypond: Very large beginning of measure spacing gap, codesite-noreply, 20:45
  • Issue 59 in lilypond: rest collision engraver should take note durations into account., codesite-noreply, 20:11
  • Issue 391 in lilypond: using relative filepath in \include "foo.ly", codesite-noreply, 20:07
  • Re: (attn doc team) Re: Diatonic notation system, Trevor Daniels, 09:09
• January 13, 2009
  • No menu, Julio, 09:25
• January 12, 2009
  • FW: [frogs] Should _all_ lilypond functions be listed in music-functions-init.ly?, Carl D. Sorensen, 19:44
  • FW: [frogs] my contribution: barCheckNumber to endSpanners, Carl D. Sorensen, 19:38
  • FW: [frogs] indentation, Carl D. Sorensen, 19:35
  • Re: programming error: when \break used before \grace or after \afterGrace in combination with proportional notation, V!ctor Adán, 11:21
  • Re: Error in FAQ, Graham Percival, 07:36
• January 11, 2009
  • Re: Issue 726 in lilypond: Wrong accidentals alignment when a second occurs simultaneously, Joe Neeman, 22:21
  • Re: Issue 726 in lilypond: Wrong accidentals alignment when a second occurs simultaneously, Valentin Villenave, 21:37
  • Re: Issue 726 in lilypond: Wrong accidentals alignment when a second occurs simultaneously, Joe Neeman, 21:13
  • Issue 726 in lilypond: Request: accidentals in the same octave would look better not aligned (in some cases), codesite-noreply, 20:06
  • Re: Issue 726 in lilypond: Wrong accidentals alignment when a second occurs simultaneously, Mark Polesky, 20:04
  • Issue 726 in lilypond: Request: accidentals in the same octave would look better not aligned (in some cases), codesite-noreply, 19:40
  • Re: Issue 726 in lilypond: Wrong accidentals alignment when a second occurs simultaneously, Valentin Villenave, 19:36
  • Issue 726 in lilypond: Wrong accidentals alignment when a second occurs simultaneously, codesite-noreply, 19:24
  • Re: Issue 726 in lilypond: Wrong accidentals alignment when a second occurs simultaneously, Mark Polesky, 19:15
  • Issue 726 in lilypond: Wrong accidentals alignment when a second occurs simultaneously, codesite-noreply, 18:07
  • Issue 724 in lilypond: Staves that begin with an accidental should have more space before their first note., codesite-noreply, 15:22
  • Re: Issue 724 in lilypond: Staves that begin with an accidental should have more space before their first note., Mark Polesky, 15:12
  • Issue 722 in lilypond: newline inside @macro{} in texinfo screws up, codesite-noreply, 13:09
  • Re: (attn doc team) Re: Diatonic notation system, Valentin Villenave, 09:56
  • Re: Non-standard octave-limited key signature does not persist, Valentin Villenave, 09:51
  • Issue 733 in lilypond: Non-standard octave-limited key signature does not persist, codesite-noreply, 09:51
  • Re: Issue 722 in lilypond: newline inside @macro{} in texinfo screws up, Valentin Villenave, 09:46
  • Re: docs: Stems info in "Editorial annotations" section?, Valentin Villenave, 09:45
  • Re: Error in FAQ, Valentin Villenave, 09:42
  • Re: [frogs] Re: Wrong MIDI instrument name, Graham Percival, 09:22
  • Issue 709 in lilypond: Simultaneous simple expressions affected to a same Staff collide by default., codesite-noreply, 09:16
  • Re: horizontally centering denominator in compound time signatures, Valentin Villenave, 09:10
  • Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils., codesite-noreply, 09:09
  • convert-ly fails to convert commands that are immediately followed by braces., Valentin Villenave, 08:58
  • Re: printing marks on every staff moves measure number up, Valentin Villenave, 08:50
  • Re: [frogs] Re: Wrong MIDI instrument name, Carl D. Sorensen, 08:48
  • Issue 731 in lilypond: \break can not be used together with \grace in proportional notation., codesite-noreply, 08:37
  • Re: programming error: when \break used before \grace or after \afterGrace in combination with proportional notation, Valentin Villenave, 08:36
  • Issue 730 in lilypond: AccidentalPlacement should take 'left-padding into account, codesite-noreply, 08:31
  • Re: AccidentalPlacement ignores left-padding, Valentin Villenave, 08:30
  • Issue 729 in lilypond: MIDI #47 instrument's name is incorrect, codesite-noreply, 08:27
  • Re: Wrong MIDI instrument name, Valentin Villenave, 08:26
  • Issue 726 in lilypond: Wrong accidentals alignment when a second occurs simultaneously, codesite-noreply, 08:20
  • Re: Font-cache broken again in 2.11.63 On Windows XP, Valentin Villenave, 08:17
  • Re: accidental shifts left as it nears a 2nd (interval), Valentin Villenave, 08:16
  • Issue 728 in lilypond: Fingerings collide with accidentals., codesite-noreply, 08:16
  • Re: Accidental hiding fingering indication, Valentin Villenave, 08:13
  • Issue 570 in lilypond: Articulations can collide with ties, codesite-noreply, 08:12
  • Issue 708 in lilypond: convert-ly fails to convert keySignature, codesite-noreply, 08:08
  • Issue 722 in lilypond: newline inside @macro{} in texinfo screws up, codesite-noreply, 07:49
  • Re: pedal glyphs top-aligned instead of bottom-aligned, Valentin Villenave, 07:45
  • Issue 727 in lilypond: Pedal "*" glyph should be bottom-aligned, codesite-noreply, 07:45
  • Issue 726 in lilypond: Wrong accidentals alignment when a second occurs in another voice, codesite-noreply, 07:41
  • Re: improper alignment of 2 accidentals in the presence of a 2nd (interval), Valentin Villenave, 07:40
  • Re: "p" and "f" dynamic glyphs align differently, Valentin Villenave, 07:31
  • Issue 725 in lilypond: "p" and "f" dynamics should be aligned in the same way, codesite-noreply, 07:28
  • Re: not enough space after prefatory matter if accidental comes first, Valentin Villenave, 07:23
  • Issue 724 in lilypond: Staves that begin with an accidental should have more space before their first note., codesite-noreply, 07:22
  • Issue 723 in lilypond: wrong horizontal alignement of pedal brackets with a second inside a chord, codesite-noreply, 07:19
  • Re: Bug in Piano Pedal instructions, Valentin Villenave, 07:18
  • Re: Issue 722 in lilypond: newline inside @macro{} in texinfo screws up, Graham Percival, 07:18
  • Issue 722 in lilypond: newline inside @macro{} in texinfo screws up, codesite-noreply, 07:10
  • Issue 722 in lilypond: newline inside @macro{} in texinfo screws up, codesite-noreply, 00:00
• January 10, 2009
  • Re: Doc - explaining layout dimensions, Graham Percival, 23:22
  • Re: use of Ambitus_engraver in DrumStaff causes program crash, Graham Percival, 20:12
  • Re: use of Ambitus_engraver in DrumStaff causes program crash, Neil Puttock, 19:26
  • use of Ambitus_engraver in DrumStaff causes program crash, Jesse Engle, 15:11
  • Re: Doc - explaining layout dimensions, Mark Polesky, 15:03
  • Doc - explaining layout dimensions, Robin Bannister, 04:28
  • Re: Snippets documentation, Graham Percival, 03:48
• January 09, 2009
  • cross-staff beaming forces rest above the system, Andrew Hawryluk, 15:08
• January 08, 2009
  • Re: Bug: dyadic accidental overprint, Trevor Bača, 01:13
• January 07, 2009
  • Re: Bug: dyadic accidental overprint, Neil Puttock, 18:22
  • Issue 721 in lilypond: Dynamics can collide with notes when applied to cross-staff voices, codesite-noreply, 10:24
  • Re: Are cross-staff beams and 'remove-empty *really* not compatible?, Graham Percival, 06:15
  • Re: Are cross-staff beams and 'remove-empty *really* not compatible?, Valentin Villenave, 06:04
  • Re: Are cross-staff beams and 'remove-empty *really* not compatible?, Graham Percival, 05:05
  • Re: downloading, Graham Percival, 05:04
  • Issue 705 in lilypond: Cross-staff beams collision (wrong stems direction), codesite-noreply, 04:08
  • Re: The crescendo mark with crescTextCresc, partcombine was ignored., T. Kiriyama, 02:13
• January 06, 2009
  • Re: The crescendo mark with crescTextCresc, partcombine was ignored., Carl D. Sorensen, 22:29
  • Bug: dyadic accidental overprint, Trevor Bača, 22:12
  • The crescendo mark with crescTextCresc, partcombine was ignored., T. Kiriyama, 19:59
  • Are cross-staff beams and 'remove-empty *really* not compatible?, Valentin Villenave, 18:21
  • Re: downloading, Carl D. Sorensen, 12:44
• January 05, 2009
  • downloading, andy, 14:20
• January 03, 2009
  • Issue 699 in lilypond: unwanted character changes on Windows Vista, codesite-noreply, 13:25
  • Not every sustainOn command works properly in midi output, Michael Pozhidaev, 13:11
  • Issue 720 in lilypond: incorrect bbox values for EPS images, codesite-noreply, 09:28
  • Re: Not every sustainOn command works properly in midi output, Trevor Daniels, 05:36
  • showLastLength and \break, Alard de Boer, 05:12
  • Fwd: No more "warning: unterminated (de)crescendo" in 2.12?, Alard de Boer, 04:21
  • Not every sustainOn command works properly in midi output, Michael Pozhidaev, 01:01
• January 02, 2009
  • Re: Issue 719 in lilypond: New Version statement not accepted, Graham Percival, 20:53
  • Re: text missing, James E. Bailey, 18:26
  • Re: text missing, Mats Bengtsson, 17:46
  • Re: Issue 719 in lilypond: New Version statement not accepted, Carl D. Sorensen, 12:55
  • Re: Issue 719 in lilypond: New Version statement not accepted, sdfgsdhdshd, 08:13
  • Re: Strange parsing of define output-suffix "AA", Villum Sejersen, 03:40
• January 01, 2009
  • Issue 719 in lilypond: New Version statement not accepted, codesite-noreply, 19:01
  • Issue 719 in lilypond: New Version statement not accepted, codesite-noreply, 18:37
  • Issue 719 in lilypond: New Version statement not accepted, codesite-noreply, 18:08
  • wrong number of arguments to font-file-as-ps-string, Dan Eble, 09:57

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc