Comment #3 on issue 1173 by pnorcks: LilyPond crash when using
showLastLength with \compressFullBarRests
http://code.google.com/p/lilypond/issues/detail?id=1173
That was probably an obvious comment. I don't really use showLastLength
that often... :)
_
Comment #2 on issue 1173 by pnorcks: LilyPond crash when using
showLastLength with \compressFullBarRests
http://code.google.com/p/lilypond/issues/detail?id=1173
Also note that no segfault occurs when the multi-measure rest "length"
agrees with the time signature:
showLastLength = R2.
{
Updates:
Status: Fixed
Labels: fixed_2_13_28
Comment #4 on issue 1155 by pnorcks: remove MODULE_GC_KLUDGE blocks from
the code base
http://code.google.com/p/lilypond/issues/detail?id=1155
Hi Ian,
The code changes look fine, so I've pushed those:
http://git.savannah.gnu.org/g
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Low
New issue 1178 by Carl.D.Sorensen: Measure_grouping_engraver uses
non-standard signs
http://code.google.com/p/lilypond/issues/detail?id=1178
As currently implemented, the measure_grouping_engraver uses a triangle for
groups
Updates:
Status: Fixed
Labels: fixed_2_13_28
Comment #1 on issue 1177 by pnorcks: Transposing a clef by interval "0"
leads to incorrect output
http://code.google.com/p/lilypond/issues/detail?id=1177
The snippet above is now rendered correctly, and warnings are output for
the
Comment #3 on issue 570 by lilyli...@googlemail.com: Articulations can
collide with ties
http://code.google.com/p/lilypond/issues/detail?id=570
Just another example of a - very standard - notation that causes a
collision between Tie and articulation
Attachments:
Tie-accent.preview
Comment #4 on issue 570 by lilyli...@googlemail.com: Articulations can
collide with ties
http://code.google.com/p/lilypond/issues/detail?id=570
\relative e'{
2~->
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/m
Status: Fixed
Owner: pnorcks
Labels: Type-Defect Priority-High fixed_2_13_28
New issue 1177 by pnorcks: Transposing a clef by interval "0" leads to
incorrect output
http://code.google.com/p/lilypond/issues/detail?id=1177
http://lists.gnu.org/archive/html/bug-lilypond/2010-07/msg00039.html
%%
On 07/08/2010 01:34 PM, Graham Percival wrote:
On Thu, Jul 08, 2010 at 10:32:10PM +0200, Urs Liska wrote:
Why don't I get my mail delivered while I can find it in the archives?
(->
http://lists.gnu.org/archive/html/bug-lilypond/2010-07/msg00064.html).
Did anybody else get this mail?
I saw that
On 07/08/10 15:32, Urs Liska wrote:
Why don't I get my mail delivered while I can find it in the archives?
(-> http://lists.gnu.org/archive/html/bug-lilypond/2010-07/msg00064.html).
Did anybody else get this mail?
Best
Urs
___
bug-lilypond mailing lis
On Thu, Jul 8, 2010 at 11:58 AM, Patrick McCarty wrote:
> On Mon, Jul 5, 2010 at 8:19 AM, Phil Holmes wrote:
>> I've been experimenting with transposing clefs to write a snippet, and found
>> that if you try to transpose a clef with a zero transposition, you actually
>> get 2. Trying 2 gives no
On Thu, Jul 08, 2010 at 10:32:10PM +0200, Urs Liska wrote:
> Why don't I get my mail delivered while I can find it in the archives?
> (->
> http://lists.gnu.org/archive/html/bug-lilypond/2010-07/msg00064.html).
> Did anybody else get this mail?
I saw that email, and this one. Our mailing lists
Why don't I get my mail delivered while I can find it in the archives?
(-> http://lists.gnu.org/archive/html/bug-lilypond/2010-07/msg00064.html).
Did anybody else get this mail?
Best
Urs
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.
On Mon, Jul 5, 2010 at 8:19 AM, Phil Holmes wrote:
> I've been experimenting with transposing clefs to write a snippet, and found
> that if you try to transpose a clef with a zero transposition, you actually
> get 2. Trying 2 gives no clef at all. Trying 1 (for what it's worth) gives
> a clef bu
On Thu, Jul 8, 2010 at 5:33 AM, Didi Kanjahn wrote:
>
> All 3 columns in the Khmer example below have a different height.
> The latest version tested was 2.13.23-1.
[...]
> Further below a second example using a Khmer Unicode font, but with Roman
> script
> letters only. Here all columns have t
On Thu, Jul 8, 2010 at 3:24 AM, Ralph Palmer wrote:
> Greetings, Didi -
>
> One more step, please : I cannot find your original email. Please submit a
> minimal example so we can add this as an issue.
Hi Ralph,
This is an issue with Pango, so the bug should be filed on the GNOME
bug tracker (htt
> I'm not top-posting
All 3 columns in the Khmer example below have a different height.
The latest version tested was 2.13.23-1.
The font selected in the first example is a Microsoft font, but any Khmer
Unicode font I have tested shows the same behavior. The font 'Khmer UI' that
comes with Windows
Ralph Palmer gmail.com> writes:
>
> Greetings, Didi -
>
> One more step, please : I cannot find your original email. Please submit a
> minimal example so we can add this as an issue.
>
> Ralph
>
Hi Ralph,
The original post was on 5 May.
Here is a minimal example:
\version "2.13.3"
\marku
On 7/8/10 1:51 AM, "Arno Waschk" wrote:
> Dear list,
>
> in the following example i would have hoped for two whole-bar beams, but
> only the second is printed like i expected.
>
>
> \version "2.13.28"
>
> {
> \overrideBeamSettings #'Staff #'(5 . 16) #'end
> #'((* . (1))
> )
Greetings, Didi -
One more step, please : I cannot find your original email. Please submit a
minimal example so we can add this as an issue.
Ralph
On Tue, Jul 6, 2010 at 4:18 AM, Didi Kanjahn wrote:
> Patrick McCarty gmail.com> writes:
>
> [...]
> > >
> > > I suspect that the bug was introduc
Hi,
there is an issue with the documentation that gave me a very hard time
to understand the concept of changing automatic beaming behaviour. So I
suggest an enhancement to the doc page.
When reading through the section "Setting automatic beam behaviour" I
encounter this passage:
The en
Dear list,
in the following example i would have hoped for two whole-bar beams, but
only the second is printed like i expected.
\version "2.13.28"
{
\overrideBeamSettings #'Staff #'(5 . 16) #'end
#'((* . (1))
)
\time 5/16 \times 10/9{c16 c16. c16 c16}
\overrideBeamSet
On Thu, Jul 8, 2010 at 12:07 AM, Trevor Daniels wrote:
>
> When I run lilypond-book with 2.13.26 I always get the
> error messages below. Lilypond-book with 2.13.14 does
> not show this error on the same files. I've not yet
> tried any releases in between. Does this os.pipe()
> error ring any b
Updates:
Status: Verified
Comment #12 on issue 1092 by lilyli...@googlemail.com: Overriding
head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT
causes segfault
http://code.google.com/p/lilypond/issues/detail?id=1092
(No comment was entered for this change.)
24 matches
Mail list logo
