Issue 485 in lilypond: please make #(ly:export(lilypond-version) safe

2007-12-17 Thread codesite-noreply
Issue 485: please make #(ly:export(lilypond-version) safe http://code.google.com/p/lilypond/issues/detail?id=485 Comment #4 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner o

Issue 485 in lilypond: please make #(ly:export(lilypond-version) safe

2007-11-26 Thread codesite-noreply
Issue 485: please make #(ly:export(lilypond-version) safe http://code.google.com/p/lilypond/issues/detail?id=485 Comment #3 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_36 -- You received this message because

Issue 485 in lilypond: please make #(ly:export(lilypond-version) safe

2007-09-30 Thread codesite-noreply
Issue 485: please make #(ly:export(lilypond-version) safe http://code.google.com/p/lilypond/issues/detail?id=485 Comment #2 by gpermus: %{ This example is flagged as `unsafe'. %} %% Do not edit this file; it is auto-generated from LSR! \header{ texidoc = " @unnumbered Ancient Music This docum

Issue 485 in lilypond: please make #(ly:export(lilypond-version) safe

2007-09-30 Thread codesite-noreply
Issue 485: please make #(ly:export(lilypond-version) safe http://code.google.com/p/lilypond/issues/detail?id=485 Comment #1 by hanwenn: Can you give more context? .ly snippet please. -- You received this message because you are listed in the owner or CC fields of this issue, or because you sta

Issue 485 in lilypond: please make #(ly:export(lilypond-version) safe

2007-09-29 Thread codesite-noreply
Issue 485: please make #(ly:export(lilypond-version) safe http://code.google.com/p/lilypond/issues/detail?id=485 New issue report by gpermus: It would be nice if there was a "safe" (ie lilypond -dsafe) command that did #(ly:export(lilypond-version). This would reduce the number of false positives