Comment #36 on issue 2356 by mts...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356#c36
Uses derived_mark to avoid segfault
http://codereview.appspot.com/5729051
___
bug-lilypond mailing list
bug-lilypond@gnu.or
Updates:
Labels: Patch-new
Comment #35 on issue 2356 by mts...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356#c35
Uses derived_mark to avoid segfault
http://codereview.appspot.com/5729051
___
bug-lilypo
Updates:
Labels: Patch-new
Comment #96 on issue 2148 by mts...@gmail.com: vertical skylines should use
stencil integrals
http://code.google.com/p/lilypond/issues/detail?id=2148#c96
Gets vertical skylines from grob stencils
http://codereview.appspot.com/5626052
_
Comment #34 on issue 2356 by mts...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
Sorry for the suggestion about axis_group_ clearing. Now that I've read it
closely, I completely understand what I wrote.
The reason I don't clear out the map is cuz it'
Comment #33 on issue 2356 by d...@gnu.org: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
Ok Mike, I was trying to change this. It starts out with
Grob *vertical_alignment = Grob::get_root_vertical_alignment
((*axis_groups_.begin ()).first);
if (!vertical_align
Comment #32 on issue 2356 by n.putt...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
Hehe, it's slightly worrying you suggest that, seeing as you coded it. I
don't have the faintest idea what the engraver actually does. :)
___
Comment #31 on issue 2356 by mts...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
I take it back then...I generally assume that when something looks wrong, I
screwed it up, but there is a slight chance that I made it that way on
purpose. I need to sle
Comment #30 on issue 2356 by n.putt...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
You can't clear it at every timestep. That was the first fix I tried a few
weeks ago. It breaks span-bar-allow-span-bar.ly.
Comment #29 on issue 2356 by mts...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
Go for it with the weak-key Scheme hash table - the garbage collection
stuff is a bit over my head, but if it works, that's great! Otherwise, you
can stay w/ the derived
Updates:
Labels: -Patch-new Patch-needs_work
Comment #6 on issue 2344 by aleksandr.andr...@gmail.com: Kievan final
barline gets cut off
http://code.google.com/p/lilypond/issues/detail?id=2344
I've changed the width and height parameters of the bar line character.
However, the problem
Updates:
Labels: Patch-new
Comment #5 on issue 2344 by aleksandr.andr...@gmail.com: Kievan final
barline gets cut off
http://code.google.com/p/lilypond/issues/detail?id=2344#c5
Fixing height of Kievan bar line
Kievan bar line is cut off when running lilypond with -dpreview,
or using
Status: Accepted
Owner:
Labels: Type-Enhancement
New issue 2377 by v.villen...@gmail.com: Enhancement: ancient cross-shaped
ornament (prall)
http://code.google.com/p/lilypond/issues/detail?id=2377
(I'm adding this directly to the tracker to save the Bug Squad a couple of
minutes.)
Fr
Comment #28 on issue 2356 by d...@gnu.org: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
Since axis_groups_ is used for mapping grobs to contexts (and not the other
way round), it would appear to make sense to implement it as a weak-key
Scheme hash table. That w
Comment #27 on issue 2356 by philehol...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
Ditto - 64 bit Ubuntu. Haipeng's crashed on .31; finishes (with errors in
the log) on patched .32 version.
___
bug-lily
Comment #26 on issue 2356 by n.putt...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
Works for me on both scores.
I too was a bit concerned that axis_groups_ hangs around. It's obviously
required between timesteps (I tried clearing it in
stop_transla
Updates:
Labels: Patch-review
Comment #25 on issue 2356 by d...@gnu.org: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356#c25
Patchy the autobot says: LGTM. Passes basic tests on a 32bit system (like
before the fix). Feedback from 64bit testers is required.
Comment #24 on issue 2356 by d...@gnu.org: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
And the whole process_acknowledged is one steaming heap of undocumented
incomprehensible contorted...
And I repeat: where is axis_group_ ever cleared out again?
___
Updates:
Labels: Patch-new
Comment #23 on issue 2356 by d...@gnu.org: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356#c23
Issue 2356: Segfault in spanbars.
This protects the contexts in the internal data structure
axis_groups_. Incidentally, this looks like t
Updates:
Labels: -Patch-new Patch-needs_work
Comment #22 on issue 2356 by d...@gnu.org: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
Mike, we have the following:
class Span_bar_stub_engraver : public Engraver
{
vector spanbars_;
map axis_groups_;
_None_
Comment #1 on issue 2365 by d8val...@gmail.com: Add 'tabloid' (as valid
string) to paper.scm
http://code.google.com/p/lilypond/issues/detail?id=2365
While we're at it, it would be nice to enable "ledger" (17x11) --
noted in paper.scm but not included for some reason.
___
Comment #21 on issue 2356 by d...@gnu.org: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
"protecting" is an operation with permanent performance and memory impact
during the life time of protection, so it is a bad idea to do it in
situations where the pairing is
Le 3 mars 2012 à 15:53, James a écrit :
> Nicolas,
>
> On 2 March 2012 12:20, Nicolas Sceaux wrote:
>> Hi,
>>
>> Using today's git LilyPond, the following snippet gives weird results:
>> the footnote is printed several times in header and footer, and on
>> several pages.
>> [...]
>>
> http://
Updates:
Status: Verified
Comment #18 on issue 2246 by carl.d.s...@gmail.com: beaming in 3/4 - a
setting to not beam 3 eights against the beat.
http://code.google.com/p/lilypond/issues/detail?id=2246
(No comment was entered for this change.)
_
Comment #20 on issue 2356 by mts...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
Hey all,
I don't have time to run regtests on the proposed patch, so my apologies if
it doesn't work. Both of the problematic files make it thru to compilation
with thi
Updates:
Labels: Patch-new
Comment #19 on issue 2356 by mts...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356#c19
Protects contexts in Span_bar_stub_engraver
http://codereview.appspot.com/5727050
___
bu
Nicolas,
On 2 March 2012 12:20, Nicolas Sceaux wrote:
> Hi,
>
> Using today's git LilyPond, the following snippet gives weird results:
> the footnote is printed several times in header and footer, and on
> several pages.
>
> \version "2.15.32"
>
> \paper {
> oddHeaderMarkup = \markup\null
> eve
Hi,
Using today's git LilyPond, the following snippet gives weird results:
the footnote is printed several times in header and footer, and on
several pages.
\version "2.15.32"
\paper {
oddHeaderMarkup = \markup\null
evenHeaderMarkup = \markup\null
oddFooterMarkup = \markup\null
evenFoote
Comment #2 on issue 2373 by philehol...@gmail.com: Windows Start Menu short
cut to 'Examples' is invalid
http://code.google.com/p/lilypond/issues/detail?id=2373
I've still got the 2.12.3 install on my machine, and it's not there,
either...
___
On 3/3/2012 10:17 AM, David Kastrup wrote:
James writes:
On 3 March 2012 09:11, David Kastrup wrote:
No. It means that we start counting again, and so far, we have not
counted a single beat because a cadenza does not count.
The manual
bar line does not change that. You can probably writ
Updates:
Labels: -Type-Crash Type-Critical
Comment #18 on issue 2356 by mts...@gmail.com: Lilypond segfaults
http://code.google.com/p/lilypond/issues/detail?id=2356
I'm marking this as critical just because it is a regression and I don't
think a stable release should go out that causes
James writes:
> On 3 March 2012 09:11, David Kastrup wrote:
>
>> No. It means that we start counting again, and so far, we have not
>> counted a single beat because a cadenza does not count.
>>
The manual
bar line does not change that. You can probably write something like
<< {
Updates:
Labels: -Patch-new Patch-review
Comment #95 on issue 2148 by d...@gnu.org: vertical skylines should use
stencil integrals
http://code.google.com/p/lilypond/issues/detail?id=2148
mensural-ligatures: the second BL. In size26, B and Largo are getting too
cozy without any need
David,
On 3 March 2012 09:11, David Kastrup wrote:
> James writes:
>
>> On 3 March 2012 08:55, David Kastrup wrote:
>>> David Bobroff writes:
>>>
I got a surprise when a cancelling accidental was printed at the
beginning of a measure. This happened following a cadenza. Short
e
Updates:
Summary: Windows Start Menu short cut to 'Examples' is invalid
Labels: -Type-Documentation Type-Build
Comment #1 on issue 2373 by pkx1...@gmail.com: Windows Start Menu short cut
to 'Examples' is invalid
http://code.google.com/p/lilypond/issues/detail?id=2373
This is n
Comment #14 on issue 2346 by d...@gnu.org: Use convert-ly from latest
development release for LSR updates
http://code.google.com/p/lilypond/issues/detail?id=2346
2.15.32-1 will very likely be next, and there is nothing to be done with
this issue (I corrected the tag when I posted my explana
Comment #4 on issue 2374 by d...@gnu.org: Placement of dot depending on
\stemDown or \voiceTwo
http://code.google.com/p/lilypond/issues/detail?id=2374
Issue 1266 talks about literature regarding dot position when voicing. I
am also pretty sure that we recently had a discussion about voicin
Updates:
Status: Invalid
Labels: -Patch-needs_work
Comment #6 on issue 2275 by pkx1...@gmail.com: Patch: Doc: simplify example
for unpure-pure containers
http://code.google.com/p/lilypond/issues/detail?id=2275
(No comment was entered for this change.)
___
Comment #3 on issue 2374 by elu...@gmail.com: Placement of dot depending on
\stemDown or \voiceTwo
http://code.google.com/p/lilypond/issues/detail?id=2374
tbh - I didn't expect anything special, it just struck me when I saw the
difference.
Janek, I can follow your argumentation (and I agr
Comment #13 on issue 2346 by pkx1...@gmail.com: Use convert-ly from latest
development release for LSR updates
http://code.google.com/p/lilypond/issues/detail?id=2346
I think what is being said here is that it *is* in the tree but missed the
window of opportunity to be in 2.15.31-1 but will
Comment #2 on issue 2374 by pkx1...@gmail.com: Placement of dot depending
on \stemDown or \voiceTwo
http://code.google.com/p/lilypond/issues/detail?id=2374
On 3 March 2012 03:20, Keith OHara wrote:
..
\voiceTwo sets the directions of all the usual notation elements that
are placed different
James writes:
> On 3 March 2012 08:55, David Kastrup wrote:
>> David Bobroff writes:
>>
>>> I got a surprise when a cancelling accidental was printed at the
>>> beginning of a measure. This happened following a cadenza. Short
>>> example below:
>>>
>>>
>>> %%%
>>> \version "2.14.2"
>>>
>>> \r
Updates:
Labels: Patch-review
Comment #6 on issue 2327 by d...@gnu.org: Doc for preview command line
option is hard to understand
http://code.google.com/p/lilypond/issues/detail?id=2327#c6
Patchy the autobot says: LGTM.
___
bug-lilypond ma
Updates:
Labels: Patch-review
Comment #2 on issue 2375 by d...@gnu.org: Patch: add ly:book-set-header!
http://code.google.com/p/lilypond/issues/detail?id=2375#c2
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
bug-lilypond@gnu.or
David,
On 3 March 2012 08:55, David Kastrup wrote:
> David Bobroff writes:
>
>> I got a surprise when a cancelling accidental was printed at the
>> beginning of a measure. This happened following a cadenza. Short
>> example below:
>>
>>
>> %%%
>> \version "2.14.2"
>>
>> \relative c'
>> {
>>
David Bobroff writes:
> I got a surprise when a cancelling accidental was printed at the
> beginning of a measure. This happened following a cadenza. Short
> example below:
>
>
> %%%
> \version "2.14.2"
>
> \relative c'
> {
> \key c \major
> \cadenzaOn
> fis4 g a b
> \cadenzaOff
> \ba
Hello,
On 3 March 2012 08:11, David Bobroff wrote:
> I got a surprise when a cancelling accidental was printed at the beginning
> of a measure. This happened following a cadenza. Short example below:
>
>
> %%%
> \version "2.14.2"
>
> \relative c'
> {
> \key c \major
> \cadenzaOn
> fis4 g a b
Keith,
On 3 March 2012 03:27, Keith OHara wrote:
> Colin Hall gmail.com> writes:
>
>> Thanks for the report, Nicolas, but 2.15.32 is not yet released
>> so I can't accept this bug report.
>
> That's unfortunate. What if I see the same problem in 2.15.27 ?
Then we have a winner!
http://code.go
Status: Accepted
Owner:
Labels: Type-Defect
New issue 2376 by pkx1...@gmail.com: Automatic footnotes on \null markups
causes unexpected results
http://code.google.com/p/lilypond/issues/detail?id=2376
Nicolas Sceaux writes:
Hi,
Using today's git LilyPond, the following snippet gives we
I got a surprise when a cancelling accidental was printed at the
beginning of a measure. This happened following a cadenza. Short
example below:
%%%
\version "2.14.2"
\relative c'
{
\key c \major
\cadenzaOn
fis4 g a b
\cadenzaOff
\bar "|"
f
}
%%%
Is this a bug?
-David
__
49 matches
Mail list logo
