Issue 334: setting staff size not longer safe
http://code.google.com/p/lilypond/issues/detail?id=334
Comment #6 by v.villenave:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or CC fie
Issue 334: setting staff size not longer safe
http://code.google.com/p/lilypond/issues/detail?id=334
Comment #5 by hanwenn:
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
Issue 334: setting staff size not longer safe
http://code.google.com/p/lilypond/issues/detail?id=334
Comment #4 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_48
--
You received this message because you are listed
Issue 334: setting staff size not longer safe
http://code.google.com/p/lilypond/issues/detail?id=334
Comment #3 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Accepted
--
You received this message because you are listed in the owner
or CC fields
Issue 334: setting staff size not longer safe
http://code.google.com/p/lilypond/issues/detail?id=334
Comment #2 by gpermus:
Really?! To clarify, I'm talking about lilypond raising an error with
-dsafe
It's a nitpick (err, sorry, should have been Priority-Low), but in a previous
version
it _was
Issue 334: setting staff size not longer safe
http://code.google.com/p/lilypond/issues/detail?id=334
Comment #1 by hanwenn:
works for me
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
