Comment #1 on issue 1554 by k-ohara5...@oco.net: Midi2ly has hardcoded LP
version
http://code.google.com/p/lilypond/issues/detail?id=1554
The LilyPond output of midi2ly conforms to a particular version of
LilyPond, which is written into the \version "x.xx.xx" in its LilyPond
output.
In
Comment #6 on issue 1533 by colinpkc...@gmail.com: midi2ly makes octave
mistakes for subsequent voices in relative mode
http://code.google.com/p/lilypond/issues/detail?id=1533
Added as issue 1554
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Status: Accepted
Owner:
Labels: Type-Scripts Priority-Low
New issue 1554 by colinpkc...@gmail.com: Midi2ly has hardcoded LP version
http://code.google.com/p/lilypond/issues/detail?id=1554
The version of Lilypond written into the .ly file output by midi2ly is
hardcoded at line 959. This sh
On Wed, Mar 9, 2011 at 2:05 PM, James Lowe wrote:
> Phil, Jeremy
>
> -Original Message-
> From: Phil Holmes
> Date: Wed, 9 Mar 2011 18:35:07 +
> To: bug-lilypond
> Subject: Re: \pitchedTrill causes warning when used with tie
>
>>"Jeremy Crabtree" wrote in message
>>news:loom.2011030
> "Neil" == Neil Puttock writes:
Neil> On 9 March 2011 16:02, Laura Conrad wrote:
>> Unfortunately, it creates a new one. In some cases, such as the
>> attached small example, when I use this BarType I get a lot of errors:
>>
>> programming error: Loose column does not
On 9 March 2011 16:02, Laura Conrad wrote:
> Unfortunately, it creates a new one. In some cases, such as the
> attached small example, when I use this BarType I get a lot of errors:
>
> programming error: Loose column does not have right side to attach to.
>
> I was hoping these loose columns we
Updates:
Labels: -Patch-review Patch-needs_work
Comment #6 on issue 737 by colinpkc...@gmail.com: Enhancement: support for
footnotes and/or endnotes.
http://code.google.com/p/lilypond/issues/detail?id=737
New patch http://codereview.appspot.com/4244064/ was pushed today. I
applied
Phil, Jeremy
-Original Message-
From: Phil Holmes
Date: Wed, 9 Mar 2011 18:35:07 +
To: bug-lilypond
Subject: Re: \pitchedTrill causes warning when used with tie
>"Jeremy Crabtree" wrote in message
>news:loom.20110309t183202-...@post.gmane.org...
>> This code
>>
>> \relative c''
>>
Comment #3 on issue 1553 by k-ohara5...@oco.net: Staff stretching problem
in 2.13.50+
http://code.google.com/p/lilypond/issues/detail?id=1553
but where exactly do you propose that \noBreak should be placed?
I should have used the plural. \noBreak s at every bar in the troublesome
line w
"Jeremy Crabtree" wrote in message
news:loom.20110309t183202-...@post.gmane.org...
This code
\relative c''
{
\pitchedTrill b1~\startTrillSpan c | b2.~ b8\stopTrillSpan r8
}
\version "2.13.51"
Will result in:
pitchedtrillbug.ly:3:17: warning: unterminated tie
\pitchedTrill b1~
Graham,
-Original Message-
From: Graham Percival
Date: Wed, 9 Mar 2011 12:52:59 +
To: James Lowe
Cc: Keith OHara , bug-lilypond
Subject: Re: Staff Stretching problem in 2.13.50+
>On 3/9/11, James Lowe wrote:
>> Actually if you go back to my example that I reported this with
>>
>>
Comment #2 on issue 1553 by percival.music.ca: Staff stretching problem in
2.13.50+
http://code.google.com/p/lilypond/issues/detail?id=1553
Sorry for a case of the stupids, but where exactly do you propose that
\noBreak should be placed? With 2.13.47 (sorry, old version), putting
\noBrea
This code
\relative c''
{
\pitchedTrill b1~\startTrillSpan c | b2.~ b8\stopTrillSpan r8
}
\version "2.13.51"
Will result in:
pitchedtrillbug.ly:3:17: warning: unterminated tie
\pitchedTrill b1~
\startTrillSpan c | b2.~ b8\stopTrillSpan r8
On 3/9/2011 5:34 PM, Graham Percival wrote:
On Wed, Mar 09, 2011 at 02:38:12PM +, David Bobroff wrote:
On 3/9/2011 2:31 PM, Phil Holmes wrote:
In this example the indentation is off. The second last '}'
should be indented. The '--->' causes this. With just '--' or
Which part of LilyPond
Comment #1 on issue 1553 by k-ohara5...@oco.net: Staff stretching problem
in 2.13.50+
http://code.google.com/p/lilypond/issues/detail?id=1553
2.12.3 also tries to make the spacing similar on successive lines. The
newer versions just to a better job of it.
\relative c'' {
c1 \break
\r
On Wed, Mar 09, 2011 at 02:38:12PM +, David Bobroff wrote:
> On 3/9/2011 2:31 PM, Phil Holmes wrote:
> >>In this example the indentation is off. The second last '}'
> >>should be indented. The '--->' causes this. With just '--' or
> >
> >Which part of LilyPond produces this "bug"?
> >
>
> W
James Lowe datacore.com> writes:
>
> \header {
> title = "S C H E R Z O"
> }
>
> \relative c'' {
> \time 3/8
> \compressFullBarRests
> R1*19*3/8 \break| cis4. | d8 r r | R1*2*3/8 | cis4. | d8 r r | \break
> R1*20*3/8
> }
>
> There is no \markup.
>
I meant markup in the general sense of t
> "Neil" == Neil Puttock writes:
Neil> On 8 March 2011 18:05, Laura Conrad wrote:
>> Does anyone know a way to tell lily that an "empty" barline shouldn't
>> have space, but there should still be some space around the barlines
>> that are being printed?
Neil> If you're r
On 3/9/2011 2:31 PM, Phil Holmes wrote:
wrote in message
news:1125644853.15867881299659748513.javamail.r...@z-mbox-02.simnet.is...
I'm not top posting.
In this example the indentation is off. The second last '}' should
be indented. The '--->' causes this. With just '--' or '->' the
inde
wrote in message
news:1125644853.15867881299659748513.javamail.r...@z-mbox-02.simnet.is...
I'm not top posting.
In this example the indentation is off. The second last '}' should be
indented. The '--->' causes this. With just '--' or '->' the indentation
works fine. Also, with '--->' em
Comment #5 on issue 1533 by philehol...@googlemail.com: midi2ly makes
octave mistakes for subsequent voices in relative mode
http://code.google.com/p/lilypond/issues/detail?id=1533
Could you add an issue report to make this non-hard-coded, please?
___
On 11-03-09 05:52 AM, Graham Percival wrote:
\version "2.13.53"
\header {
% removing the title changes the spacing of the c1 c c c line below!
title = "title"
}
\relative c'' {
\compressFullBarRests
R1*4
\break
% this will either be spaced on two systems (including the title)
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1553 by colinpkc...@gmail.com: Staff stretching problem in
2.13.50+
http://code.google.com/p/lilypond/issues/detail?id=1553
It seems that any markup on the page causes version 2.13.50+ to prefer
stretching the lines,
On 3/9/11, James Lowe wrote:
> Actually if you go back to my example that I reported this with
>
> \header {
> title = "S C H E R Z O"
> }
>
> \relative c'' {
> \time 3/8
> \compressFullBarRests
> R1*19*3/8 \break| cis4. | d8 r r | R1*2*3/8 | cis4. | d8 r r | \break
> R1*20*3/8
> }
In which
Keith,
-Original Message-
From: Keith OHara
Date: Wed, 9 Mar 2011 08:18:17 +
To: bug-lilypond
Subject: Re: Staff Stretching problem in 2.13.50+
>> It seems that any markup on the page causes version 2.13.50+ to prefer
>> stretching the lines, if one line was forced to be stretched.
Updates:
Status: Verified
Labels: -Patch-review fixed_2_13_54
Comment #3 on issue 1541 by percival.music.ca: [PATCH] Cleaning Feta flags
code (issue4236043)
http://code.google.com/p/lilypond/issues/detail?id=1541
Pushed.
___
bug-li
> I'm not top posting.
In this example the indentation is off. The second last '}' should be
indented. The '--->' causes this. With just '--' or '->' the indentation
works fine. Also, with '--->' emacs complains of "mismatched parentheses" when
the final '}' is entered. All indentation fo
Comment #1 on issue 1552 by k-ohara5...@oco.net: Style 'voice accidentals
incorrectly typeset when two voices immediately preceded by different
single voice
http://code.google.com/p/lilypond/issues/detail?id=1552
To see the point of this issue, without suffering a worse problem, you need
> It seems that any markup on the page causes version 2.13.50+ to prefer
> stretching the lines, if one line was forced to be stretched.
> ---
> \version "2.13.51"
> \score {\relative c'' {
> c1 c \break
> d1 d d d d d d d
> } }
> \markup "hello"
>
[...]
> I think this is a bug/regression.
>
Prob
29 matches
Mail list logo
