Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2)

2011-07-04 Thread lilypond
Comment #7 on issue 1014 by brownian.box: Full/multi measure rests should be semibreve (for any but 4/2) http://code.google.com/p/lilypond/issues/detail?id=1014 Thanks for the fix! However, since the Summary contains "(for any but 4/2)", I would like to mention that lilypond seems to be un

Switcing accidental style doesn't always work

2011-07-04 Thread Ole Vedel Villumsen
> I'm not top posting. In a piano composition I chose #(set-accidental-style 'piano-cautionary), but a few of the reminders (cautionary accidentals) seemed more confusing than helpful. I thought I could switch to 'default. I could, it worked; but then I couldn't switch back to 'piano-cautionary ag

Issue 1737 in lilypond: Add table of predefined fretboards for ukulele and mandolin to NR Appendices

2011-07-04 Thread lilypond
Status: Accepted Owner: Labels: Type-Documentation Priority-Medium New issue 1737 by carl.d.s...@gmail.com: Add table of predefined fretboards for ukulele and mandolin to NR Appendices http://code.google.com/p/lilypond/issues/detail?id=1737 NR A.4 has all the predefined fretboards for gu

Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }

2011-07-04 Thread lilypond
Updates: Labels: -Patch-new Patch-review Comment #6 on issue 1734 by pkx1...@gmail.com: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } } http://code.google.com/p/lilypond/issues/detail?id=1734 Passes make and reg tests. _

Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura)

2011-07-04 Thread lilypond
Updates: Labels: -Patch-new Patch-review Comment #16 on issue 75 by pkx1...@gmail.com: Slurs cannot be nested (including acciaccatura and appoggiatura) http://code.google.com/p/lilypond/issues/detail?id=75 Make succeeds, and reg tests look ok, but there is one note in one of the .ly

Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2)

2011-07-04 Thread lilypond
Updates: Labels: -fixed_2_14_2 syntax_change Comment #6 on issue 1014 by carl.d.s...@gmail.com: Full/multi measure rests should be semibreve (for any but 4/2) http://code.google.com/p/lilypond/issues/detail?id=1014 Thanks, you're right. So at this point, we've declared this bug to b

Research on ties (was: Odd-looking tie on a chord)

2011-07-04 Thread Janek Warchoł
2011/7/4 m...@apollinemike.com : > We always strive to have the best out-of-the-box result possible, so if you > feel after experimenting with these settings that you arrive at a result that > is more akin to what you see in musical rep, send us a scan of the rep and > the parameters you used to

Re: after \once \set fingeringOrientations… Lilypond falls back to #up

2011-07-04 Thread -Eluze
Dmytro O. Redchuk-2 wrote: > > pps. Let's continue with "\once \set" issue. > sure - i'll try to summarize: \set deals with context properties \override deals with grob properties \override stacks the previous settings and recalls them when \once is used \revert falls back to the "original" s

Re: Issue 1709 in lilypond: Add feta-flags to build system

2011-07-04 Thread lilypond
Comment #4 on issue 1709 by lemniska...@gmail.com: Add feta-flags to build system http://code.google.com/p/lilypond/issues/detail?id=1709 New patch passes regtests. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/l

Issue 1736 in lilypond: clarify description of minimal examples

2011-07-04 Thread lilypond
Status: Started Owner: Labels: Type-Documentation Priority-Low Patch-review New issue 1736 by lemniska...@gmail.com: clarify description of minimal examples http://code.google.com/p/lilypond/issues/detail?id=1736 http://codereview.appspot.com/4636082/ __

Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2)

2011-07-04 Thread lilypond
Comment #5 on issue 1014 by n.putt...@gmail.com: Full/multi measure rests should be semibreve (for any but 4/2) http://code.google.com/p/lilypond/issues/detail?id=1014 Carl, I think you've marked this as fixed_2_14_2 by mistake: 104f80 can't be backported since it removes a grob property.

Issue 1735 in lilypond: modifying default behaviour of tremolo slashes

2011-07-04 Thread lilypond
Status: Started Owner: lemniska...@gmail.com Labels: Patch-review Priority-Medium Type-Defect New issue 1735 by lemniska...@gmail.com: modifying default behaviour of tremolo slashes http://code.google.com/p/lilypond/issues/detail?id=1735 http://lists.gnu.org/archive/html/lilypond-user/2011-06

Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals

2011-07-04 Thread lilypond
Comment #12 on issue 1701 by carl.d.s...@gmail.com: default accidental style prints too many 'extra' naturals http://code.google.com/p/lilypond/issues/detail?id=1701 fixed_2_14_2 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu

Re: Issue 1643 in lilypond: Part Combine problems

2011-07-04 Thread lilypond
Updates: Labels: -backport fixed_2_14_2 Comment #9 on issue 1643 by carl.d.s...@gmail.com: Part Combine problems http://code.google.com/p/lilypond/issues/detail?id=1643 Backported ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lis

Re: Issue 1714 in lilypond: Build error regarding mf2pt1 with latest texlive (2011) and lilypond

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_2 Comment #7 on issue 1714 by carl.d.s...@gmail.com: Build error regarding mf2pt1 with latest texlive (2011) and lilypond http://code.google.com/p/lilypond/issues/detail?id=1714 backported ___ bug-lilypond maili

Re: Issue 1714 in lilypond: Build error regarding mf2pt1 with latest texlive (2011) and lilypond

2011-07-04 Thread lilypond
Comment #8 on issue 1714 by carl.d.s...@gmail.com: Build error regarding mf2pt1 with latest texlive (2011) and lilypond http://code.google.com/p/lilypond/issues/detail?id=1714 backported ___ bug-lilypond mailing list bug-lilypond@gnu.org https://l

Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655

2011-07-04 Thread lilypond
Updates: Labels: syntax_change Comment #12 on issue 1716 by carl.d.s...@gmail.com: No convert-ly rule for the fix for issue 1655 http://code.google.com/p/lilypond/issues/detail?id=1716 Can't be backported due to syntax change ___ bug-lilyp

Re: Issue 1682 in lilypond: Website version links need updating

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_2 Comment #11 on issue 1682 by carl.d.s...@gmail.com: Website version links need updating http://code.google.com/p/lilypond/issues/detail?id=1682 Backported ___ bug-lilypond mailing list bug-lilypond@gnu.org htt

Re: Issue 1692 in lilypond: Spanner::calc_normalized_endpoints is broken for line-spanners

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_2 Comment #5 on issue 1692 by carl.d.s...@gmail.com: Spanner::calc_normalized_endpoints is broken for line-spanners http://code.google.com/p/lilypond/issues/detail?id=1692 backported ___ bug-lilypond mailing lis

Re: Issue 1706 in lilypond: Beaming causes lilypond to crash

2011-07-04 Thread lilypond
Comment #9 on issue 1706 by carl.d.s...@gmail.com: Beaming causes lilypond to crash http://code.google.com/p/lilypond/issues/detail?id=1706 You will make it much easier to backport if you will include a commit number in the comment when you change the status to fixed. Thanks, Carl ___

Re: Issue 1706 in lilypond: Beaming causes lilypond to crash

2011-07-04 Thread lilypond
Updates: Labels: -backport fixed_2_14_2 Comment #8 on issue 1706 by carl.d.s...@gmail.com: Beaming causes lilypond to crash http://code.google.com/p/lilypond/issues/detail?id=1706 Backported ___ bug-lilypond mailing list bug-lilypond@gnu.o

Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2)

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_2 Comment #4 on issue 1014 by carl.d.s...@gmail.com: Full/multi measure rests should be semibreve (for any but 4/2) http://code.google.com/p/lilypond/issues/detail?id=1014 (No comment was entered for this change.) _

Re: Issue 1617 in lilypond: chordGlissando is a hack that should be replaced with a Glissando property such as 'connect-all

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_0 Comment #3 on issue 1617 by carl.d.s...@gmail.com: chordGlissando is a hack that should be replaced with a Glissando property such as 'connect-all http://code.google.com/p/lilypond/issues/detail?id=1617 (No comment was entered for this change.)

Re: Issue 1043 in lilypond: Cross-staff beams confuse skyline calculations

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_2 Comment #15 on issue 1043 by carl.d.s...@gmail.com: Cross-staff beams confuse skyline calculations http://code.google.com/p/lilypond/issues/detail?id=1043 Backported ___ bug-lilypond mailing list bug-lilypond@

Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters

2011-07-04 Thread lilypond
Updates: Labels: -fixed_2-14_0 fixed_2_14_0 Comment #11 on issue 1502 by carl.d.s...@gmail.com: Document information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 (No comment was entered for this change.)

Re: Issue 487 in lilypond: stems of beamed notes too long before staff change

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_2 Comment #12 on issue 487 by carl.d.s...@gmail.com: stems of beamed notes too long before staff change http://code.google.com/p/lilypond/issues/detail?id=487 Backported ___ bug-lilypond mailing list bug-lilypon

Re: Issue 1467 in lilypond: [PATCH] Doc: Rewrite NR 3.2 Titles and headers. (issue3667041)

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_0 Comment #9 on issue 1467 by carl.d.s...@gmail.com: [PATCH] Doc: Rewrite NR 3.2 Titles and headers. (issue3667041) http://code.google.com/p/lilypond/issues/detail?id=1467 (No comment was entered for this change.) _

Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters

2011-07-04 Thread lilypond
Updates: Labels: fixed_2-14_0 Comment #10 on issue 1502 by carl.d.s...@gmail.com: Document information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 (No comment was entered for this change.) __

Re: Issue 1547 in lilypond: Too many colliding rests

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_2 Comment #7 on issue 1547 by carl.d.s...@gmail.com: Too many colliding rests http://code.google.com/p/lilypond/issues/detail?id=1547 Backported ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.

Re: Issue 1607 in lilypond: patch for mandolin freboard diagrams

2011-07-04 Thread lilypond
Comment #6 on issue 1607 by carl.d.s...@gmail.com: patch for mandolin freboard diagrams http://code.google.com/p/lilypond/issues/detail?id=1607 Was part of 2.14.0. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/li

Re: Issue 1607 in lilypond: patch for mandolin freboard diagrams

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_0 Comment #5 on issue 1607 by carl.d.s...@gmail.com: patch for mandolin freboard diagrams http://code.google.com/p/lilypond/issues/detail?id=1607 Was part of 2.14.0. ___ bug-lilypond mailing list bug-lilypond@gn

Re: Issue 1614 in lilypond: DynamicTextSpanner documentation is wrong

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_2 Comment #6 on issue 1614 by carl.d.s...@gmail.com: DynamicTextSpanner documentation is wrong http://code.google.com/p/lilypond/issues/detail?id=1614 Backported, I think ___ bug-lilypond mailing list bug-lilypo

Re: Issue 1618 in lilypond: unpredictable placement of rests

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_2 Comment #9 on issue 1618 by carl.d.s...@gmail.com: unpredictable placement of rests http://code.google.com/p/lilypond/issues/detail?id=1618 Backported ___ bug-lilypond mailing list bug-lilypond@gnu.org https:

Re: Issue 816 in lilypond: Accidentals should use the normal fontsize in figured bass

2011-07-04 Thread lilypond
Comment #3 on issue 816 by o...@villumsen.name: Accidentals should use the normal fontsize in figured bass http://code.google.com/p/lilypond/issues/detail?id=816 I see no change from 2.12.3 to 2.14.1. I think this is still an issue. Yours, Ole ___

Re: Issue 1640 in lilypond: Consecutive glissandos not typeset

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_0 Comment #4 on issue 1640 by carl.d.s...@gmail.com: Consecutive glissandos not typeset http://code.google.com/p/lilypond/issues/detail?id=1640 (No comment was entered for this change.) ___ bug-lilypond mailing

Re: Issue 1639 in lilypond: Glissando between chords at end of measure prevents break and is sometimes not printed

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_0 Comment #6 on issue 1639 by carl.d.s...@gmail.com: Glissando between chords at end of measure prevents break and is sometimes not printed http://code.google.com/p/lilypond/issues/detail?id=1639 (No comment was entered for this change.) _

Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings

2011-07-04 Thread lilypond
Updates: Labels: fixed_2_14_0 Comment #9 on issue 1626 by carl.d.s...@gmail.com: Articulate produces faulty barcheck warnings http://code.google.com/p/lilypond/issues/detail?id=1626 (No comment was entered for this change.) ___ bug-lilypon

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

2011-07-04 Thread Dmytro O. Redchuk
On Mon 04 Jul 2011, 17:15 I wrote: > On Mon 04 Jul 2011, 16:17 I wrote: > > For windows I would try to start with .cmd like this: > This seems to work (tested under VirtualBox, WinXP): Sorry for the noise, final ("initial") version is so far: rem --8<-- @echo off r

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

2011-07-04 Thread Dmytro O. Redchuk
On Mon 04 Jul 2011, 16:17 I wrote: > For windows I would try to start with .cmd like this: This seems to work (tested under VirtualBox, WinXP): rem 8<-- rem trimtagline.bat rem rem get only file name, no extension: set LY=%~n1 echo \header { tagline = ##f } | lilypond -di

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

2011-07-04 Thread Dmytro O. Redchuk
On Mon 04 Jul 2011, 15:19 Neil Puttock wrote: > On 4 July 2011 15:16, Neil Puttock wrote: > > > Ah, I didn't notice that (though it only applies to single-system > > snippets where you'd usually use -dpreview). > > Silly me. Of course, with ragged-right = ##t the same applies to > multi-system

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

2011-07-04 Thread Neil Puttock
On 4 July 2011 15:16, Neil Puttock wrote: > Ah, I didn't notice that (though it only applies to single-system > snippets where you'd usually use -dpreview). Silly me. Of course, with ragged-right = ##t the same applies to multi-system snippets. :) Cheers, Neil

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

2011-07-04 Thread Neil Puttock
On 4 July 2011 14:57, Dmytro O. Redchuk wrote: > But this gives "wide" image, with a width of paper, I guess. (And some extra > space at top... and bottom). Ah, I didn't notice that (though it only applies to single-system snippets where you'd usually use -dpreview). Cheers, Neil _

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

2011-07-04 Thread Dmytro O. Redchuk
On Mon 04 Jul 2011, 14:48 Neil Puttock wrote: > On 4 July 2011 14:17, Dmytro O. Redchuk wrote: > > > I've not tested! I have no any windows (with lilypond and ImageMagick) > > about. > > You don't need ImageMagick. The eps backend will produce a trimmed > png (assuming the tagline's been remov

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

2011-07-04 Thread Neil Puttock
On 4 July 2011 14:17, Dmytro O. Redchuk wrote: > I've not tested! I have no any windows (with lilypond and ImageMagick) about. You don't need ImageMagick. The eps backend will produce a trimmed png (assuming the tagline's been removed): echo "\\header { tagline = ##f }" | lilypond -dinclude-se

Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }

2011-07-04 Thread lilypond
Comment #5 on issue 1734 by brownian.box: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } } http://code.google.com/p/lilypond/issues/detail?id=1734 whether a crash in input file with incorrect syntax is Critical or not I'd say "that's why

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

2011-07-04 Thread Dmytro O. Redchuk
On Mon 04 Jul 2011, 07:06 Colin Campbell wrote: > Sorry for the delay, Dmytro! I was trying to find a bit of time to > test whether it, or a slightly different version, would work under > Windows. The convert command comes from ImageMagik which seems to > have a Windows binary available. For win

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

2011-07-04 Thread Colin Campbell
On 11-07-04 04:39 AM, Dmytro O. Redchuk wrote: On Thu 23 Jun 2011, 14:19 Graham Percival wrote: Colin: add this to the CG (since Dmytro isn't trained in making patches). Hi! Please, Colin, would you add this to the CG? I guess, to "8.5 Adding issues to the tracker" :) http://lilypond.org/doc/

Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }

2011-07-04 Thread lilypond
Comment #4 on issue 1734 by percival.music.ca: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } } http://code.google.com/p/lilypond/issues/detail?id=1734 I have conflicting recollection as to whether a crash in input file with incorrect sy

Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }

2011-07-04 Thread lilypond
Comment #3 on issue 1734 by brownian.box: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } } http://code.google.com/p/lilypond/issues/detail?id=1734 @mike: yes, if set as #'right in musical fragment, it produces quite correct warning. _

Re: Issue 1712 in lilypond: Braces redesigned

2011-07-04 Thread lilypond
Updates: Status: Fixed Labels: -Patch-review fixed_2_15_5 Comment #3 on issue 1712 by percival.music.ca: Braces redesigned http://code.google.com/p/lilypond/issues/detail?id=1712 (No comment was entered for this change.) ___ bug-lilyp

Re: after \once \set fingeringOrientations… Lilypond falls back to #up

2011-07-04 Thread Dmytro O. Redchuk
On Mon 04 Jul 2011, 05:15 -Eluze wrote: > \version "2.15.2" > > \layout { > \context { > \Score > fingeringOrientations = #'right > } > } > { } > > if i have no fingering it does not crash! > > cheers > Eluze Thank you, added as 1734: http://code.google.com/p/lilypond/issues/detail

Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }

2011-07-04 Thread lilypond
Updates: Labels: Patch-new Comment #2 on issue 1734 by mts...@gmail.com: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } } http://code.google.com/p/lilypond/issues/detail?id=1734 The issue is that fingering orientations needs to be

Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }

2011-07-04 Thread lilypond
Updates: Summary: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } } Comment #1 on issue 1734 by brownian.box: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } } http://code.google.com/p/l

Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura)

2011-07-04 Thread lilypond
Comment #15 on issue 75 by reinhold...@gmail.com: Slurs cannot be nested (including acciaccatura and appoggiatura) http://code.google.com/p/lilypond/issues/detail?id=75 Make problem is fixed now. New patch up: http://codereview.appspot.com/4643067 ___

Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" with simple fingerings

2011-07-04 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Critical New issue 1734 by brownian.box: Lilypond crashes on "fingeringOrientations = #'right" with simple fingerings http://code.google.com/p/lilypond/issues/detail?id=1734 Reported by Eluze, http://lists.gnu.org/archive/html/bug-lily

Re: after \once \set fingeringOrientations… Lilypond falls back to #up

2011-07-04 Thread -Eluze
Dmytro O. Redchuk-2 wrote: > > On Mon 04 Jul 2011, 04:22 -Eluze wrote: >> btw: writing fingeringOrientations = #'right brings Lilypond to crash! > It does not here (ubuntu linux 64bit): > > $ cat test.ly > \relative { > \once \set fingeringOrientations = #'right > < e -1> > } > > > > $ L

Re: after \once \set fingeringOrientations… Lilypond falls back to #up

2011-07-04 Thread Dmytro O. Redchuk
On Mon 04 Jul 2011, 04:22 -Eluze wrote: > btw: writing fingeringOrientations = #'right brings Lilypond to crash! It does not here (ubuntu linux 64bit): $ cat test.ly \relative { \once \set fingeringOrientations = #'right < e -1> } $ LANG=C lilypond test.ly GNU LilyPond 2.14.1 Processing `.

Re: after \once \set fingeringOrientations… Lilypond falls back to #up

2011-07-04 Thread -Eluze
Dmytro O. Redchuk-2 wrote: > > On Mon 04 Jul 2011, 01:43 -Eluze wrote: >> the code >> >> \relative { >> \set fingeringOrientations = #'(left) >> < e -1>1 | >> \once \set fingeringOrientations = #'(right) >> < e -1> | >> < e -1> | >> } >> >> produces >> http://old.nabble.com/file/p3

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

2011-07-04 Thread Dmytro O. Redchuk
On Thu 23 Jun 2011, 14:19 Graham Percival wrote: > Colin: add this to the CG (since Dmytro isn't trained in making > patches). Hi! Please, Colin, would you add this to the CG? I guess, to "8.5 Adding issues to the tracker" :) http://lilypond.org/doc/v2.15/Documentation/contributor/adding-issues-t

Re: Odd-looking tie on a chord

2011-07-04 Thread m...@apollinemike.com
On Jul 4, 2011, at 11:45 AM, Dmytro O. Redchuk wrote: > On Mon 04 Jul 2011, 15:39 James Harkins wrote: >> \version "2.14.1" >> >> \include "english.ly" >> >> \score { >> \new Staff { >> \key d \major >> \numericTimeSignature >> \time 4/4 >> r4 >> \times 4/5 { 16\< > d'' b''>~ } >> 16

Re: Issue 1126 in lilypond: Tie positioning not as expected

2011-07-04 Thread lilypond
Comment #1 on issue 1126 by brownian.box: Tie positioning not as expected http://code.google.com/p/lilypond/issues/detail?id=1126 Another examples from this thread: http://lists.gnu.org/archive/html/lilypond-user/2011-07/msg00049.html % ---8< \version "2.14.1" \

Re: Odd-looking tie on a chord

2011-07-04 Thread Dmytro O. Redchuk
On Mon 04 Jul 2011, 15:39 James Harkins wrote: > \version "2.14.1" > > \include "english.ly" > > \score { > \new Staff { > \key d \major > \numericTimeSignature > \time 4/4 > r4 > \times 4/5 { 16\< b''>~ } > 16 8. > > %% Here: the tie on the D's looks funny > %

Re: after \once \set fingeringOrientations… Lilypond falls back to #up

2011-07-04 Thread Dmytro O. Redchuk
On Mon 04 Jul 2011, 01:43 -Eluze wrote: > the code > > \relative { > \set fingeringOrientations = #'(left) > < e -1>1 | > \once \set fingeringOrientations = #'(right) > < e -1> | > < e -1> | > } > > produces > http://old.nabble.com/file/p31987692/chord%2Bfingering%2Bsmall.jpg > > >

Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi

2011-07-04 Thread lilypond
Updates: Status: Started Comment #6 on issue 1728 by brownian.box: Implements multi-line non-cross staff glissandi http://code.google.com/p/lilypond/issues/detail?id=1728 So, I make it "Started". Thanks! ___ bug-lilypond mailing list bug-l

after \once \set fingeringOrientations… Lilypond falls back to #up

2011-07-04 Thread -Eluze
the code \relative { \set fingeringOrientations = #'(left) < e -1>1 | \once \set fingeringOrientations = #'(right) < e -1> | < e -1> | } produces http://old.nabble.com/file/p31987692/chord%2Bfingering%2Bsmall.jpg imo the fingering in the 3rd "chord" should be at the left of the no

Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi

2011-07-04 Thread lilypond
Comment #5 on issue 1728 by mts...@gmail.com: Implements multi-line non-cross staff glissandi http://code.google.com/p/lilypond/issues/detail?id=1728 I thought it was fixed because I didn't realize a gotchya about regtest bounding boxes applied to glissandos (I should have been able to conn

Re: Issue 1542 in lilypond: [PATCH] Add springs-and-rods callback to DynamicTextSpanner, so minimum-length has an effect (issue4187054)

2011-07-04 Thread lilypond
Updates: Status: Verified Comment #4 on issue 1542 by brownian.box: [PATCH] Add springs-and-rods callback to DynamicTextSpanner, so minimum-length has an effect (issue4187054) http://code.google.com/p/lilypond/issues/detail?id=1542 (No comment was entered for this change.) ___

Re: Issue 1655 in lilypond: Handles longa in MultiMeasureRest

2011-07-04 Thread lilypond
Updates: Status: Verified Comment #6 on issue 1655 by brownian.box: Handles longa in MultiMeasureRest http://code.google.com/p/lilypond/issues/detail?id=1655 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond

Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi

2011-07-04 Thread lilypond
Comment #4 on issue 1728 by brownian.box: Implements multi-line non-cross staff glissandi http://code.google.com/p/lilypond/issues/detail?id=1728 So why it was marked as Fixed? What would be correct state? ___ bug-lilypond mailing list bug-lilypon

Re: Issue 1692 in lilypond: Spanner::calc_normalized_endpoints is broken for line-spanners

2011-07-04 Thread lilypond
Updates: Status: Verified Comment #4 on issue 1692 by brownian.box: Spanner::calc_normalized_endpoints is broken for line-spanners http://code.google.com/p/lilypond/issues/detail?id=1692 (No comment was entered for this change.) ___ bug-li

Re: Issue 1708 in lilypond: Adds ly:engraver-property to engraver-scheme

2011-07-04 Thread lilypond
Updates: Status: Verified Comment #3 on issue 1708 by brownian.box: Adds ly:engraver-property to engraver-scheme http://code.google.com/p/lilypond/issues/detail?id=1708 Ok, let it be verified. ___ bug-lilypond mailing list bug-lilypond@gnu

Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi

2011-07-04 Thread lilypond
Comment #3 on issue 1728 by mts...@gmail.com: Implements multi-line non-cross staff glissandi http://code.google.com/p/lilypond/issues/detail?id=1728 This issue is still being fixed: the most current patch is at http://codereview.appspot.com/4631086/ Cheers, MS _

Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi

2011-07-04 Thread lilypond
Updates: Status: Verified Comment #2 on issue 1728 by brownian.box: Implements multi-line non-cross staff glissandi http://code.google.com/p/lilypond/issues/detail?id=1728 I am about to ignore "Patch-review" label... But shouldn't it be removed so far? ___