Updates:
Status: Verified
Comment #12 on issue 1356 by colingh...@gmail.com: LilyPond-style comments
embedded in a Scheme expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356
Verified commit present on Savannah
lilyp...@googlecode.com writes:
Updates:
Status: Verified
Comment #12 on issue 1356 by colingh...@gmail.com: LilyPond-style
comments embedded in a Scheme expression can't include special
characters
http://code.google.com/p/lilypond/issues/detail?id=1356
Verified commit present on
On Mon, Nov 28, 2011 at 10:54:31AM +0100, David Kastrup wrote:
Hm. Should we really verify already when the commit made it to
staging?
Yes. Brief discussion was 1-3 weeks ago.
That makes the state rather arbitrary. I'd wait at least
until it has migrated properly to master (since that's
Graham Percival gra...@percival-music.ca writes:
On Mon, Nov 28, 2011 at 10:54:31AM +0100, David Kastrup wrote:
Hm. Should we really verify already when the commit made it to
staging?
Yes. Brief discussion was 1-3 weeks ago.
That makes the state rather arbitrary. I'd wait at least
On Mon, Nov 28, 2011 at 11:16:55AM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Too hard for people with less than 5 hours of training to
determine.
I am not sure I understand that rationale.
git log origin
Is it there or not? Can you think of a
Graham Percival gra...@percival-music.ca writes:
On Mon, Nov 28, 2011 at 11:16:55AM +0100, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Too hard for people with less than 5 hours of training to
determine.
I am not sure I understand that rationale.
git log
Updates:
Labels: -Patch-countdown Patch-push
Comment #10 on issue 1356 by colinpkc...@gmail.com: LilyPond-style comments
embedded in a Scheme expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356
Counted down to 2027
Updates:
Owner: d...@gnu.org
Comment #6 on issue 1356 by d...@gnu.org: LilyPond-style comments embedded
in a Scheme expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356
To make an example for code that will still cause problems:
#(let
Comment #7 on issue 1356 by d...@gnu.org: LilyPond-style comments embedded
in a Scheme expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356#c7
Record $ and # expressions inside of #{ #} for better correlation
This improves and robustifies the
Updates:
Labels: -Patch-new Patch-review
Comment #8 on issue 1356 by pkx1...@gmail.com: LilyPond-style comments
embedded in a Scheme expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356
Passes make and reg tests.
James
Updates:
Labels: -Priority-Medium -syntax
Comment #3 on issue 1356 by pkx1...@gmail.com: LilyPond-style comments
embedded in a Scheme expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356
(No comment was entered for this change.)
Comment #2 on issue 1356 by percival.music.ca: LilyPond-style comments
embedded in a Scheme expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356
So the documentation bug is that instead of writing the $ character may
be used to introduce
Updates:
Labels: -Type-Defect Type-Documentation
Comment #1 on issue 1356 by n.puttock: LilyPond-style comments embedded in
a Scheme expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356
`read-lily-expression' says this:
Read a #{ lily
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium syntax
New issue 1356 by v.villenave: LilyPond-style comments embedded in a Scheme
expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356
% Reported by Werner:
http://lists.gnu.org
14 matches
Mail list logo
