Re: Issue 2180 in lilypond: beams are detached from stems

2012-01-16 Thread lilypond
Updates: Status: Started Owner: mts...@gmail.com Comment #15 on issue 2180 by carl.d.s...@gmail.com: beams are detached from stems http://code.google.com/p/lilypond/issues/detail?id=2180 (No comment was entered for this change.) __

Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient

2012-01-16 Thread lilypond
Updates: Status: Started Owner: carl.d.s...@gmail.com Comment #20 on issue 2100 by carl.d.s...@gmail.com: Patch: CG: explanation of branches for the impatient http://code.google.com/p/lilypond/issues/detail?id=2100 (No comment was entered for this change.) __

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

2012-01-16 Thread Carl Sorensen
After a thorough review of the literature, I'm pretty satisfied that the beaming in 2.14 was wrong. The beaming in 2.15.24 is correct. If the 2.14 beaming is desired, a workaround is shown on lilypond issue 2228: I've marked that issue

Re: Issue 2228 in lilypond: Patch: Fix beaming-pattern for compound meters

2012-01-16 Thread lilypond
Updates: Status: Invalid Labels: -Type-Ugly -Patch-new Type-Enhancement Patch-abandoned Comment #3 on issue 2228 by carl.d.s...@gmail.com: Patch: Fix beaming-pattern for compound meters http://code.google.com/p/lilypond/issues/detail?id=2228 Further review of the literature an

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

2012-01-16 Thread Carl Sorensen
On 1/16/12 3:41 PM, "Janek Warchoł" wrote: >Carl, > >Thanks for your research. >I agree that there must be tied notes if one wants this melody to be >in 3/4 meter. >However, i'm not sure about 6/8. My "pure reasoning" is that a >measure in 6/8 meter divides like this: > >4. + 4. >8+8+8 + 8+8+8

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

2012-01-16 Thread Janek Warchoł
Carl, 2012/1/16 Carl Sorensen : > Having reviewed Gould on beaming, I don't believe that the 3/4 time > measure in this example shows a valid problem. > > The rhythm in the 3/4 measure is an invalid measure.  The three beats in > the measure are combined in such a way that the beats are obscured,

Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default.

2012-01-16 Thread lilypond
Comment #19 on issue 2070 by carl.d.s...@gmail.com: Patch: Don't wrap EventChord around rhythmic events by default. http://code.google.com/p/lilypond/issues/detail?id=2070 OK, I'm trying to understand the implications of things and respond to comments 16 and 17. I'm not sure I'm clear abou

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

2012-01-16 Thread Carl Sorensen
On 1/15/12 2:50 PM, "Martin Straeten" wrote: >> I'm not top posting. >in 6/8 an 3/4 measure the beamlet of the last/first semiwaver >points to the dotted quaver. > >semiquavers should be beamed together like in 2.14.2 > >%-sample-- >\version "2.15.24" >\score { >\relative c'{ > \time 6/8 >

Re: verbose does not work when invoked as -d option

2012-01-16 Thread -Eluze
Ralph Palmer-3 wrote: > > On Sun, Jan 15, 2012 at 10:29 AM, -Eluze wrote: > > > Is -dverbose a legitimate option? I would have thought the form would be > -d > --verbose. When I try that (lilypond -d --verbose FILENAME), I get > "warning: no such internal option: --verbose", but the score com

Re: Issue 2213 in lilypond: Update documentation for \footnotes in Notation Reference

2012-01-16 Thread lilypond
Updates: Labels: Patch-new Comment #3 on issue 2213 by pkx1...@gmail.com: Update documentation for \footnotes in Notation Reference http://code.google.com/p/lilypond/issues/detail?id=2213#c3 Doc: NR Update section on Footnotes Issue 2206 saw a rewrite of the \footnote code that there

Re: verbose does not work when invoked as -d option

2012-01-16 Thread Ralph Palmer
On Sun, Jan 15, 2012 at 10:29 AM, -Eluze wrote: > > when invoking lilypond with the command line option verbose only a few > closing brackets are printed before the help text appears: > > lilypond -dverbose=#t > > GNU LilyPond 2.15.24 > ] > ] > ] > ] > ] > ] > ] > ] > ] > ] > ] > ] > ] > ] > ] >

Re: Issue 2228 in lilypond: Patch: Fix beaming-pattern for compound meters

2012-01-16 Thread lilypond
Comment #2 on issue 2228 by carl.d.s...@gmail.com: Patch: Fix beaming-pattern for compound meters http://code.google.com/p/lilypond/issues/detail?id=2228#c2 Fix beaming-pattern for compound meters http://codereview.appspot.com/5545067 ___ bug-lil

Re: Issue 2228 in lilypond: Patch: Fix beaming-pattern for compound meters

2012-01-16 Thread lilypond
Updates: Status: Started Owner: carl.d.s...@gmail.com Labels: -Type-Enhancement Type-Ugly Regression Comment #1 on issue 2228 by carl.d.s...@gmail.com: Patch: Fix beaming-pattern for compound meters http://code.google.com/p/lilypond/issues/detail?id=2228 Issue based on

Issue 2228 in lilypond: Patch: Fix beaming-pattern for compound meters

2012-01-16 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2228 by carl.d.s...@gmail.com: Patch: Fix beaming-pattern for compound meters http://code.google.com/p/lilypond/issues/detail?id=2228 Fix beaming-pattern for compound meters http://codereview.appspot.com/5545067 _

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

2012-01-16 Thread Carl Sorensen
On 1/15/12 2:50 PM, "Martin Straeten" wrote: >> I'm not top posting. >in 6/8 an 3/4 measure the beamlet of the last/first semiwaver >points to the dotted quaver. > >semiquavers should be beamed together like in 2.14.2 > >%-sample-- >\version "2.15.24" >\score { >\relative c'{ > \time 6/8 >

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

2012-01-16 Thread Carl Sorensen
On 1/15/12 6:04 PM, "Carl Sorensen" wrote: >On 1/15/12 3:06 PM, "Janek Warchoł" wrote: > >>2012/1/15 Martin Straeten : I'm not top posting. >>> in 6/8 an 3/4 measure the beamlet of the last/first semiwaver >>> points to the dotted quaver. >>> >>> semiquavers should be beamed together >> >>I

Re: Issue 2227 in lilypond: Patch: changes.tely: mention Flag changes, remove duplicate "does"

2012-01-16 Thread lilypond
Updates: Labels: Patch-review Comment #1 on issue 2227 by lilypond...@gmail.com: Patch: changes.tely: mention Flag changes, remove duplicate "does" http://code.google.com/p/lilypond/issues/detail?id=2227#c1 Patchy the autobot says: LGTM. _

Re: Issue 2225 in lilypond: Patch: Docs: Explain the difference between ritardando and rallentando

2012-01-16 Thread lilypond
Updates: Labels: Patch-review Comment #2 on issue 2225 by lilypond...@gmail.com: Patch: Docs: Explain the difference between ritardando and rallentando http://code.google.com/p/lilypond/issues/detail?id=2225#c2 Patchy the autobot says: LGTM. _

Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient

2012-01-16 Thread lilypond
Updates: Labels: Patch-review Comment #19 on issue 2100 by lilypond...@gmail.com: Patch: CG: explanation of branches for the impatient http://code.google.com/p/lilypond/issues/detail?id=2100#c19 Patchy the autobot says: LGTM. ___ bug-lilyp

Re: Issue 2200 in lilypond: Dots shouldn't always be placed in one column

2012-01-16 Thread lilypond
Updates: Labels: Patch-review Comment #7 on issue 2200 by lilypond...@gmail.com: Dots shouldn't always be placed in one column http://code.google.com/p/lilypond/issues/detail?id=2200#c7 Patchy the autobot says: LGTM. ___ bug-lilypond maili

Re: Issue 2217 in lilypond: Chord names collide with notes (vertical space missing on second line staff)

2012-01-16 Thread lilypond
Comment #1 on issue 2217 by ja...@montignies.info: Chord names collide with notes (vertical space missing on second line staff) http://code.google.com/p/lilypond/issues/detail?id=2217 As a workaround, you can add a transparent mark: \score { << \new ChordNames = "chords" \chordmod

Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch

2012-01-16 Thread lilypond
Comment #23 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should using a "working" branch http://code.google.com/p/lilypond/issues/detail?id=2092#c23 Update lilygit.tcl (Issue 2092) Makes lilygit.tcl respect the environment variable $LILYPOND_GIT. If $LILYPOND_GIT is unset, default of

Re: Issue 2180 in lilypond: beams are detached from stems

2012-01-16 Thread lilypond
Comment #14 on issue 2180 by gra...@percival-music.ca: beams are detached from stems http://code.google.com/p/lilypond/issues/detail?id=2180 Use the -n or -c or -i or --whatever-I-called-the-don't-upload-to-code.google.com-option, then add the url manually. Otherwise, modify git-cl to i

Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient

2012-01-16 Thread lilypond
Comment #18 on issue 2100 by carl.d.s...@gmail.com: Patch: CG: explanation of branches for the impatient http://code.google.com/p/lilypond/issues/detail?id=2100#c18 Issue 2100: Explanation of branches for CG Explain branches, by Graham Percival Changes to git commands by Carl Sorensen http:

Re: Issue 2180 in lilypond: beams are detached from stems

2012-01-16 Thread lilypond
Comment #13 on issue 2180 by colinpkc...@gmail.com: beams are detached from stems http://code.google.com/p/lilypond/issues/detail?id=2180 Agreed, Keith, and thanks for the catch! For the record: the "new" status came from Mike adding a response to points Keith raised, and I gather git-cl t

Re: Issue 2180 in lilypond: beams are detached from stems

2012-01-16 Thread lilypond
Updates: Labels: -Patch-new Patch-countdown Comment #12 on issue 2180 by k-ohara5...@oco.net: beams are detached from stems http://code.google.com/p/lilypond/issues/detail?id=2180 Assuming that we don't want to extend the review cycle when patches get merely cosmetic updates... _

Re: Issue 2200 in lilypond: Dots shouldn't always be placed in one column

2012-01-16 Thread lilypond
Updates: Labels: -Patch-needs_work Patch-new Comment #5 on issue 2200 by k-ohara5...@oco.net: Dots shouldn't always be placed in one column http://code.google.com/p/lilypond/issues/detail?id=2200 After accounting for the new Flag grobs, and handling meshed chords better, I think we