[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 485 in lilypond: please make #(ly:export(lilypond-version) safe
From: |
codesite-noreply |
Subject: |
Issue 485 in lilypond: please make #(ly:export(lilypond-version) safe |
Date: |
Sat, 29 Sep 2007 13:48:02 -0700 |
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 for "potentially dangerous changes" that I need to review when
updating LSR.
I'm thinking of a markup command like
\lilyver
Cheers,
- Graham
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Enhancement Priority-Low
--
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 adjust your issue notification preferences at:
http://code.google.com/hosting/settings
- Issue 485 in lilypond: please make #(ly:export(lilypond-version) safe,
codesite-noreply <=