Comment #7 on issue 1096 by musiccomposition: ly:parser-parse-string
segfaults when directly called at toplevel
http://code.google.com/p/lilypond/issues/detail?id=1096
Attaching a patch which adds a new ly:parser-include-string interface.
Attachments:
0001-add-ly-parser-include-strin
On Sun, May 30, 2010 at 2:03 PM, Neil Puttock wrote:
> On 28 May 2010 17:48, Xavier Scheuer wrote:
>
>> Shouldn't we open an issue about this on the tracker, at least to
>> keep track on this discussion and your very interesting proposal?
>
> I should have a patch sorted later, so there's no need
Updates:
Status: Fixed
Comment #7 on issue 1103 by n.puttock: Typo in engraver name while defining
new contexts causes lilypond to segfault
http://code.google.com/p/lilypond/issues/detail?id=1103
(No comment was entered for this change.)
_
Updates:
Labels: fixed_2_13_23
Comment #6 on issue 1103 by n.puttock: Typo in engraver name while defining
new contexts causes lilypond to segfault
http://code.google.com/p/lilypond/issues/detail?id=1103
Thanks, it's applied.
Cheers,
Neil
___
Comment #5 on issue 1103 by musiccomposition: Typo in engraver name while
defining new contexts causes lilypond to segfault
http://code.google.com/p/lilypond/issues/detail?id=1103
Hopefully last patch. :)
Attachments:
0001-Don-t-segfault-on-invalid-engraver-names.patch 2.6 KB
Hi Oleksandr,
On 30/05/10 21:05, Oleksandr Gavenko wrote:
On 2010-05-30 22:07, Xavier Scheuer wrote:
2010/5/30 Oleksandr Gavenko:
If I want generate many midi fragment I repeat text
\score { \new Staff { ... }
\layout { }
\midi { }
}
as many times as need. And when I run
$ lilypond my.ly
2010/5/30 Graham Percival :
> Did you try looking on the tracker?
>
> closed, submitted, etc.
> http://code.google.com/p/lilypond/issues/detail?id=836
>
> open item:
> http://code.google.com/p/lilypond/issues/detail?id=1041
Sorry, missed that.
That would have been easier than digging out and sea
On Sun, May 30, 2010 at 10:59:57PM +0200, Xavier Scheuer wrote:
> I recently answered a question about "output suffix"
Did you try looking on the tracker?
closed, submitted, etc.
http://code.google.com/p/lilypond/issues/detail?id=836
open item:
http://code.google.com/p/lilypond/issues/detail?id=
On 28 May 2010 17:48, Xavier Scheuer wrote:
> Shouldn't we open an issue about this on the tracker, at least to
> keep track on this discussion and your very interesting proposal?
I should have a patch sorted later, so there's no need to log this on
the tracker. Once I've refreshed the (approve
Special recipients: Marek Klein, Valentin.
Hi dear Frogs!
I recently answered a question about "output suffix"
http://lists.gnu.org/archive/html/bug-lilypond/2010-05/msg00302.html
and I found out the discussion "Naming output files":
http://lists.gnu.org/archive/html/lilypond-user/2009-02/msg0080
Comment #4 on issue 1103 by n.puttock: Typo in engraver name while defining
new contexts causes lilypond to segfault
http://code.google.com/p/lilypond/issues/detail?id=1103
Thanks, that looks fine.
There's just one more thing, which I missed first time round:
This line,
SCM def =
On 2010-05-30 22:07, Xavier Scheuer wrote:
2010/5/30 Oleksandr Gavenko:
If I want generate many midi fragment I repeat text
\score { \new Staff { ... }
\layout { }
\midi { }
}
as many times as need. And when I run
$ lilypond my.ly
I get a lot of my.midi, my-1.midi, ..., my-17.midi, ..
2010/5/30 Oleksandr Gavenko :
> If I want generate many midi fragment I repeat text
>
> \score { \new Staff { ... }
> \layout { }
> \midi { }
> }
>
> as many times as need. And when I run
>
> $ lilypond my.ly
>
> I get a lot of my.midi, my-1.midi, ..., my-17.midi, ...
>
> It is possible to cont
If I want generate many midi fragment I repeat text
\score { \new Staff { ... }
\layout { }
\midi { }
}
as many times as need. And when I run
$ lilypond my.ly
I get a lot of my.midi, my-1.midi, ..., my-17.midi, ...
It is possible to control names of generated midi files
in .ly source fi
Updates:
Status: Fixed
Labels: fixed_2_13_22
Comment #8 on issue 1036 by percival.music.ca: Links to accented anchors
http://code.google.com/p/lilypond/issues/detail?id=1036
(No comment was entered for this change.)
___
bug-lilypond m
Comment #7 on issue 1036 by paconet.org: Links to accented anchors
http://code.google.com/p/lilypond/issues/detail?id=1036
The afore mentioned 'side effect' was already in the old docs; the patch
has not
touched this behaviour.
___
bug-lilypond ma
Status: Accepted
Owner:
Labels: Type-Other Priority-Low website Frog
New issue 1105 by percival.music.ca: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
We have a bunch of CSS files. AFAIK use two or three. Figure out what we
use and get rid of the rest. A
On 05/30/2010 03:52 AM, Joe Neeman wrote:
IIRC, tight-spacing just means to place lines as close together as
possible (which means a tight spring and a padding of zero).
That's what the code in page-layout-problem seems to be doing -- so I
based my patch to page-breaking on simply trying to ma
On Tue, May 18, 2010 at 10:58 AM, Boris Shingarov wrote:
> Hi Joe,
>
>
> The fact that tight-spacing ignores padding is probably a bug. Do things
work better if you change minimum_distance to (minimum_distance +
padding) in page-layout-problem.cc:286?
>>> As I had posted earl
19 matches
Mail list logo
