Re: Issue 1144 in lilypond: [PATCH] 100+ warnings (issue1724041)

Updates: Status: Verified Mergedinto: -804 Comment #2 on issue 1144 by brownian.box: [PATCH] 100+ warnings (issue1724041) http://code.google.com/p/lilypond/issues/detail?id=1144 (No comment was entered for this change.) ___ bug-li

Re: Issue 1116 in lilypond: Title not centered

Updates: Status: Verified Comment #10 on issue 1116 by brownian.box: Title not centered http://code.google.com/p/lilypond/issues/detail?id=1116 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http:

Re: Issue 1104 in lilypond: Enhancement: 'offset for \underline markup function needed (and proposed)

Updates: Status: Verified Comment #6 on issue 1104 by brownian.box: Enhancement: 'offset for \underline markup function needed (and proposed) http://code.google.com/p/lilypond/issues/detail?id=1104 (No comment was entered for this change.) ___

Re: Issue 1041 in lilypond: Output suffix for score should be documented

Updates: Status: Verified Comment #10 on issue 1041 by brownian.box: Output suffix for score should be documented http://code.google.com/p/lilypond/issues/detail?id=1041 (No comment was entered for this change.) ___ bug-lilypond mailing li

Re: Issue 1055 in lilypond: guile 2.0

Comment #9 on issue 1055 by hanwenn: guile 2.0 http://code.google.com/p/lilypond/issues/detail?id=1055 do these errors always look like that? Or do things crash badly/randomly at times? ___ bug-lilypond mailing list bug-lilypond@gnu.org http://li

Re: Issue 1055 in lilypond: guile 2.0

Comment #8 on issue 1055 by hanwenn: guile 2.0 http://code.google.com/p/lilypond/issues/detail?id=1055 Patrick, the fact that we get wrong type to apply: X where X randomly is anything but a function is really bad. It means that there is some sort of memory corruption going on. My first

Re: Problem with 2.13.30?

Am Montag, 30. August 2010, um 00:25:47 schrieben Sie: > > I don't really see any other way to turn the input path to an > > absolute path > > than calling os.path.abspath, in particular, since the input path > > can already > > be an absolute path... > > But doesn't this solution create a worse p

Re: Problem with 2.13.30?

Graham Percival wrote Monday, August 30, 2010 12:02 AM On Sun, Aug 29, 2010 at 11:25:47PM +0100, Trevor Daniels wrote: I have to copy an old version of lilypondbook into every new release in order to get a working version. We can't expect users to do that. I'm confused about what's going

Re: Problem with 2.13.30?

On Sun, Aug 29, 2010 at 11:25:47PM +0100, Trevor Daniels wrote: > > I have to copy an old version of > lilypondbook into every new release in order to get > a working version. We can't expect users to do that. I'm confused about what's going on. Are you talking about 1226 (which is claimed to b

Re: Problem with 2.13.30?

Reinhold Kainhofer wrote Sunday, August 29, 2010 8:33 PM Thanks, Trevor, for you bisecting... The culprit is actually not the refactoring, but a bug fix I did before the refactoring (commit 4da9fc65cbf74f4cbbdb01add4d5f341a16f5065 at 10.06.10 13:01). The problem I fixed with it was quite ugl

Re: Issue 1245 in lilypond: festival song output is uncompletely undocumented

Comment #2 on issue 1245 by percival.music.ca: festival song output is uncompletely undocumented http://code.google.com/p/lilypond/issues/detail?id=1245 I noticed that page, but a quick scan doesn't tell me what to do with the .xml file. I mean, I tried festival song-basic.xml but got s

Re: Problem with 2.13.30?

Am Donnerstag, 26. August 2010, um 11:04:15 schrieb Trevor Daniels: > "Phil Holmes" wrote in message > news:i53pqa$tp...@dough.gmane.org... > > Line 4 in the snippet map is > > #(ly:add-file-name-alist '(("3e/lily-0cba8859.ly" . > > "C:\Users\Trevor\LilyPond-git\Documentation\music-glossary.tely")

Re: Issue 1245 in lilypond: festival song output is uncompletely undocumented

Comment #1 on issue 1245 by markpolesky: festival song output is uncompletely undocumented http://code.google.com/p/lilypond/issues/detail?id=1245 seems pretty well documented here: http://www.freebsoft.org/singing-computer ___ bug-lilypond mailin

Issue 1245 in lilypond: festival song output is uncompletely undocumented

Status: Accepted Owner: Labels: Type-Documentation Priority-Low Frog New issue 1245 by percival.music.ca: festival song output is uncompletely undocumented http://code.google.com/p/lilypond/issues/detail?id=1245 ~/src/lilypond/Documentation$ git grep festival es/web/news.itexi:singing su

Re: Issue 1197 in lilypond: Doc: Update NR for new \tempo syntax

Comment #4 on issue 1197 by pkx1...@hotmail.com: Doc: Update NR for new \tempo syntax http://code.google.com/p/lilypond/issues/detail?id=1197 Submitted initial Patch to Graham. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.or