Issue 714 in lilypond: let the .ly file specify the output filename

2008-12-28 Thread codesite-noreply
Comment #6 on issue 714 by v.villenave: let the .ly file specify the output filename http://code.google.com/p/lilypond/issues/detail?id=714 That's because you've marked it as Verified. -- You received this message because you are listed in the owner or CC fields of this issue, or because you

Issue 717 in lilypond: make python scripts work (better) in OSX 10.4

2008-12-28 Thread codesite-noreply
Status: Accepted Owner: gpermus Labels: Type-Defect Priority-Medium New issue 717 by gpermus: make python scripts work (better) in OSX 10.4 http://code.google.com/p/lilypond/issues/detail?id=717 set TARGET_PYTHON=/usr/bin/env python for OSX in git. This is waiting for GUB3 to be added to git.

Issue 714 in lilypond: let the .ly file specify the output filename

2008-12-28 Thread codesite-noreply
Comment #5 on issue 714 by gpermus: let the .ly file specify the output filename http://code.google.com/p/lilypond/issues/detail?id=714 why the Mao is that "issue 404" displayed with strikethrough?! Anyway, the link works. -- You received this message because you are listed in the owner

Issue 714 in lilypond: let the .ly file specify the output filename

2008-12-28 Thread codesite-noreply
Comment #4 on issue 714 by gpermus: let the .ly file specify the output filename http://code.google.com/p/lilypond/issues/detail?id=714 Sorry. Issue #404. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may

Issue 714 in lilypond: let the .ly file specify the output filename

2008-12-28 Thread codesite-noreply
Comment #3 on issue 714 by hanwenn: let the .ly file specify the output filename http://code.google.com/p/lilypond/issues/detail?id=714 please link to the prev. issue. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this iss

Re: Issue 716 in lilypond: --disable-optimisation causes `Parsed object should be dead'

2008-12-28 Thread Nicolas Sceaux
Le 28 déc. 08 à 23:43, codesite-nore...@google.com a écrit : Updates: Cc: nicolas.sceaux Comment #1 on issue 716 by hanwenn: --disable-optimisation causes `Parsed object should be dead' http://code.google.com/p/lilypond/issues/detail?id=716 this was introduced between .64 and .65, I

Issue 716 in lilypond: --disable-optimisation causes `Parsed object should be dead'

2008-12-28 Thread codesite-noreply
Updates: Cc: nicolas.sceaux Comment #1 on issue 716 by hanwenn: --disable-optimisation causes `Parsed object should be dead' http://code.google.com/p/lilypond/issues/detail?id=716 this was introduced between .64 and .65, I suspect due to nic's changes for nested bookpaper. Nicolas

Issue 711 in lilypond: Filter out unknown font formats

2008-12-28 Thread codesite-noreply
Comment #3 on issue 711 by hanwenn: Filter out unknown font formats http://code.google.com/p/lilypond/issues/detail?id=711 I don't know - best to ask on the fontconfig list -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this i

Issue 714 in lilypond: let the .ly file specify the output filename

2008-12-28 Thread codesite-noreply
Updates: Status: Accepted Labels: -Priority-Low Priority-Postponed Comment #2 on issue 714 by gpermus: let the .ly file specify the output filename http://code.google.com/p/lilypond/issues/detail?id=714 Ok, I'm re-opening this since there's at least one user who'd like it.

Issue 716 in lilypond: --disable-optimisation causes `Parsed object should be dead'

2008-12-28 Thread codesite-noreply
Status: Accepted Owner: lemzwerg Labels: Type-Defect New issue 716 by lemzwerg: --disable-optimisation causes `Parsed object should be dead' http://code.google.com/p/lilypond/issues/detail?id=716 [git 2008-12-27] Even the simplest lilypond input (like `{ c }') causes programming error: Pars

Re: you links are broken

2008-12-28 Thread John Mandereau
Le dimanche 28 décembre 2008 à 16:14 +, Larry Green a écrit : > the links for the 2.12 version of Lilypond are broken. This has been fixed. -- John Mandereau ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listin

you links are broken

2008-12-28 Thread Larry Green
the links for the 2.12 version of Lilypond are broken. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Crash if \layout omitted with \midi

2008-12-28 Thread Trevor Daniels
James E. Bailey wrote Sunday, December 28, 2008 8:35 AM Am 18.12.2008 um 09:57 schrieb Mark Polesky: Trevor Daniels wrote: Using \midi without \layout in 2.11.65-1 causes an exception in Windows Vista: in XP also. - Mark In OSX 10.4 Intel also. This is fixed in 2.12. Trevor _

Re: Crash if \layout omitted with \midi

2008-12-28 Thread James E. Bailey
Am 18.12.2008 um 09:57 schrieb Mark Polesky: Trevor Daniels wrote: Using \midi without \layout in 2.11.65-1 causes an exception in Windows Vista: in XP also. - Mark In OSX 10.4 Intel also. ___ bug-lilypond mailing list bug-lilypond@gnu.org ht