Re: Issue 943 in lilypond: A slur should follow the same vertical direction it would have in unbroken state.

2009-12-20 Thread lilypond
Comment #4 on issue 943 by jameseli...@googlemail.com: A slur should follow the same vertical direction it would have in unbroken state. http://code.google.com/p/lilypond/issues/detail?id=943 Sure, a slur should follow the same vertical direction because the regtest for slur-broken-trend.l

Tempo / tuplet bracket bug

2009-12-20 Thread Trevor Bača
Hi, The following snippet exhibits a bug in the form of contention between metronome mark and tuplet instantiation: %%% BEGIN TEMPO INSTANTIATION BUG %%% \version "2.13.9" \new Staff { \time 2/8 \times 2/3 { \tempo 8=52 c'8 ( c'8 c'8 } \time 2/8 c'8

Re: horizontal alignment of dynamics attached to skips

2009-12-20 Thread Neil Puttock
2009/12/17 Reinhold Kainhofer : > Is there any way to make lilypond use the same horizontal position for s\p and > c\p ??? If you don't care about spanner alignment (i.e., hairpins/dynamic text spans), then it's possible to realign the dynamics by using NoteColumn (you can retrieve DynamicText gr

Re: Issue 492 in lilypond: piano pedal disappears during RehearsalMark

2009-12-20 Thread lilypond
Updates: Status: Started Owner: n.puttock Comment #4 on issue 492 by n.puttock: piano pedal disappears during RehearsalMark http://code.google.com/p/lilypond/issues/detail?id=492 (No comment was entered for this change.) -- You received this message because you are listed in

Re: Issue 936 in lilypond: \tempo makes TextSpanner too long

2009-12-20 Thread lilypond
Updates: Status: Duplicate Mergedinto: 492 Comment #2 on issue 936 by n.puttock: \tempo makes TextSpanner too long http://code.google.com/p/lilypond/issues/detail?id=936 (No comment was entered for this change.) -- You received this message because you are listed in the owner or

Re: Issue 492 in lilypond: piano pedal disappears during RehearsalMark

2009-12-20 Thread lilypond
Comment #3 on issue 492 by n.puttock: piano pedal disappears during RehearsalMark http://code.google.com/p/lilypond/issues/detail?id=492 Issue 936 has been merged into this issue. -- You received this message because you are listed in the owner or CC fields of this issue, or because you star

Issue 946 in lilypond: build tarballs of docs

2009-12-20 Thread lilypond
Status: Accepted Owner: Labels: Type-Other Priority-Postponed New issue 946 by percival.music.ca: build tarballs of docs http://code.google.com/p/lilypond/issues/detail?id=946 We want tarballs (or maybe zip, if windows doesn't support .tar.bz2) of: - all split HTML docs - all big HTML docs

Re: Issue 928 in lilypond: `Dynamics' items aren't vertically centered

2009-12-20 Thread lilypond
Updates: Status: Fixed Labels: fixed_2_13_10 Comment #1 on issue 928 by n.puttock: `Dynamics' items aren't vertically centered http://code.google.com/p/lilypond/issues/detail?id=928 (No comment was entered for this change.) -- You received this message because you are listed

Re: Issue 837 in lilypond: Unnecessary empty dirs in Win32 builds

2009-12-20 Thread lilypond
Comment #6 on issue 837 by pkx1...@hotmail.com: Unnecessary empty dirs in Win32 builds http://code.google.com/p/lilypond/issues/detail?id=837 Yes the control panel uninstall does the same thing - takes a long time You can watch the files vanish one at a time, and I am able to simply 'del' t

Re: Issue 837 in lilypond: Unnecessary empty dirs in Win32 builds

2009-12-20 Thread lilypond
Comment #5 on issue 837 by pkx1...@hotmail.com: Unnecessary empty dirs in Win32 builds http://code.google.com/p/lilypond/issues/detail?id=837 originally I was going to report this on 2.13.9 and 2.13.8 (I think), but I see that it does the same thing for me on windows 7 for 2.12.3 when I run

Re: Issue 837 in lilypond: Unnecessary empty dirs in Win32 builds

2009-12-20 Thread lilypond
Updates: Status: Accepted Labels: -fixed_2_13_8 Comment #4 on issue 837 by percival.music.ca: Unnecessary empty dirs in Win32 builds http://code.google.com/p/lilypond/issues/detail?id=837 There's a credible report that this is broken in 2.13.9 and 2.12.3. -- You received this

Re: Issue 945 in lilypond: warning about \version for short snippets

2009-12-20 Thread Mark Polesky
> Currently we show a warning if there's no \version > statement. This is teh suck for the tutorial -- do we > explain that people need to write > \version "2.12.0" > before they've even learned what > { c'4 } > means, or do we let their first view of lilypond be a > warning? Neither. Just l

Re: Issue 945 in lilypond: warning about \version for short snippets

2009-12-20 Thread lilypond
Comment #1 on issue 945 by lemzwerg: warning about \version for short snippets http://code.google.com/p/lilypond/issues/detail?id=945 I'm not willing to work on it, but I have to make a comment anyway, since it sounds that you want to have a poll... I prefer #1: (a) it's the simplest solut

Issue 945 in lilypond: warning about \version for short snippets

2009-12-20 Thread lilypond
Status: Accepted Owner: Labels: Type-Enhancement Priority-Low New issue 945 by percival.music.ca: warning about \version for short snippets http://code.google.com/p/lilypond/issues/detail?id=945 Don't discuss this issue unless you're seriously willing to work on it -- putting patches, or

Issue 944 in lilypond: settings for less than 1 (full) line

2009-12-20 Thread lilypond
Status: Accepted Owner: Labels: Type-Enhancement Priority-Low New issue 944 by percival.music.ca: settings for less than 1 (full) line http://code.google.com/p/lilypond/issues/detail?id=944 Don't discuss this issue unless you're seriously willing to work on it -- putting patches, organising

Re: Issue 932 in lilypond: Vertical spacing: repeat brackets and tablatures exceeding page bottom

2009-12-20 Thread lilypond
Updates: Status: Fixed Labels: fixed_2_13_10 Comment #1 on issue 932 by joeneeman: Vertical spacing: repeat brackets and tablatures exceeding page bottom http://code.google.com/p/lilypond/issues/detail?id=932 (No comment was entered for this change.) -- You received this mess

Re: Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil

2009-12-20 Thread lilypond
Updates: Status: Fixed Labels: fixed_2_13_10 Comment #8 on issue 628 by n.puttock: Regression: markup \note doesn't work as a TimeSignature stencil http://code.google.com/p/lilypond/issues/detail?id=628 (No comment was entered for this change.) -- You received this message be

Re: Issue 943 in lilypond: A slur should follow the same vertical direction it would have in unbroken state.

2009-12-20 Thread lilypond
Comment #3 on issue 943 by lemzwerg: A slur should follow the same vertical direction it would have in unbroken state. http://code.google.com/p/lilypond/issues/detail?id=943 And please format the example so that its description is in texinfo format -- and it should compile! (Your code abo

Re: Issue 943 in lilypond: A slur should follow the same vertical direction it would have in unbroken state.

2009-12-20 Thread lilypond
Comment #2 on issue 943 by percival.music.ca: A slur should follow the same vertical direction it would have in unbroken state. http://code.google.com/p/lilypond/issues/detail?id=943 Why should a slur blah blah blah? (hint: specify the filename. That way, we know that you're speaking from

Re: Issue 943 in lilypond: A slur should follow the same vertical direction it would have in unbroken state.

2009-12-20 Thread lilypond
Updates: Labels: Type-Defect Comment #1 on issue 943 by jameseli...@googlemail.com: A slur should follow the same vertical direction it would have in unbroken state. http://code.google.com/p/lilypond/issues/detail?id=943 (No comment was entered for this change.) -- You received this

Issue 943 in lilypond: A slur should follow the same vertical direction it would have in unbroken state.

2009-12-20 Thread lilypond
Status: Accepted Owner: Labels: Priority-Regression New issue 943 by jameseli...@googlemail.com: A slur should follow the same vertical direction it would have in unbroken state. http://code.google.com/p/lilypond/issues/detail?id=943 A slur should follow the same vertical direction it wo

Re: Catching up on bugs

2009-12-20 Thread James Bailey
In checking the regressions, I've come across some issues. And, sorry for posting these all in one go, but I've just been saving them up until one day I could post a massive email and have the bug tracker explode with new regression issues. Regressions: page-label.ly: line 35: \mark \marku

Re: Issue 867 in lilypond: lilypond-book can have hash collisions

2009-12-20 Thread lilypond
Updates: Labels: -Type-Enhancement Type-Other Comment #3 on issue 867 by percival.music.ca: lilypond-book can have hash collisions http://code.google.com/p/lilypond/issues/detail?id=867 On Fri, Dec 18, 2009 at 2:38 AM, Han-Wen adds: We already have a plausible explanation, and a fair

Issue 942 in lilypond: out-www/web/ has upper-case and lower-case filenames

2009-12-20 Thread lilypond
Status: Accepted Owner: Labels: Type-Other Priority-Low Maintainability New issue 942 by percival.music.ca: out-www/web/ has upper-case and lower-case filenames http://code.google.com/p/lilypond/issues/detail?id=942 gperc...@gperciva-desktop:~/src/build-lilypond/Documentation$ ls -lh out

Re: Issue 940 in lilypond: unify announcement methods

2009-12-20 Thread lilypond
Comment #2 on issue 940 by percival.music.ca: unify announcement methods http://code.google.com/p/lilypond/issues/detail?id=940 I'm not logging into any webpage. Does it have a command-line client that can be driven by a python script? If not, then no thanks. -- You received this message b

Re: Issue 938 in lilypond: building lilypond omf files: what, why, how, etc

2009-12-20 Thread lilypond
Updates: Labels: -Type-Documentation Type-Other Comment #3 on issue 938 by percival.music.ca: building lilypond omf files: what, why, how, etc http://code.google.com/p/lilypond/issues/detail?id=938 How are they used: I mean, does anybody use them? If I go to a repository of open-so

Re: Issue 941 in lilypond: Enhancement: merging make-markup-command and make-builtin-markup-command

2009-12-20 Thread lilypond
Updates: Cc: nicolas.sceaux Comment #1 on issue 941 by v.villenave: Enhancement: merging make-markup-command and make-builtin-markup-command http://code.google.com/p/lilypond/issues/detail?id=941 I understand Nicolas is on it (or something like that). -- You received this message bec

Re: Enhancement request: make-markup-command cleanup and docs

2009-12-20 Thread Valentin Villenave
On Sun, Dec 20, 2009 at 11:01 AM, David Kastrup wrote: > The current state of make-markup-command is less than satisfactory since > make-markup-command and make-builtin-markup-command have different > syntaxes and semantics, making the latter an "insider" command that > complicates the transition

Issue 941 in lilypond: Enhancement: merging make-markup-command and make-builtin-markup-command

2009-12-20 Thread lilypond
Status: Started Owner: v.villenave Labels: Priority-Medium Type-Enhancement Maintainability Patch New issue 941 by v.villenave: Enhancement: merging make-markup-command and make-builtin-markup-command http://code.google.com/p/lilypond/issues/detail?id=941 New request from David Kastrup: """

Re: Issue 940 in lilypond: unify announcement methods

2009-12-20 Thread lilypond
Comment #1 on issue 940 by v.villenave: unify announcement methods http://code.google.com/p/lilypond/issues/detail?id=940 If we want to go social-networking, there are unified platforms for this: http://ping.fm/networks/ -- You received this message because you are listed in the owner or CC fie

Re: Issue 938 in lilypond: building lilypond omf files: what, why, how, etc

2009-12-20 Thread lilypond
Updates: Labels: -Type-Other Type-Documentation Comment #2 on issue 938 by v.villenave: building lilypond omf files: what, why, how, etc http://code.google.com/p/lilypond/issues/detail?id=938 Then perhaps we should just document this somewhere? Honestly, I'm not sure this discussio

Enhancement request: make-markup-command cleanup and docs

2009-12-20 Thread David Kastrup
The current state of make-markup-command is less than satisfactory since make-markup-command and make-builtin-markup-command have different syntaxes and semantics, making the latter an "insider" command that complicates the transition from advanced user to Lilypond contributor. There has been wor