Graham Percival writes:
> On Sun, Aug 28, 2011 at 08:00:14PM +, d...@gnu.org wrote:
>> It would be a pity not to make it available to users.
>
> Do you want to dump something in changes.tely to let users know
> about this?
Good idea. Consider it done yesterday.
--
David Kastrup
_
On Sun, Aug 28, 2011 at 08:00:14PM +, d...@gnu.org wrote:
> It would be a pity not to make it available to users.
Do you want to dump something in changes.tely to let users know
about this?
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-
I have decided to be an ass and push this change. It touches
astonishingly little code, is surprisingly useful and simplifies
extending Lilypond considerably, passes the regtests, and I like its
code.
It would be a pity not to make it available to users. The programming
documentation, in spite
Ok, I guess this is as good as it gets. I've put in some uses in
programming-interfaces.itely particularly in connection with markups and
markup lists, and I feel that this makes dealing with a number of things
more pleasant.
For example, the markup macro should rarely if ever be needed anymore.
Reviewers: nicolas.sceaux,
Message:
This passes regtests. I would tend towards committing in this form in
order to keep commit size to the point. Instead of a separate regtest,
I'd likely walk through scm and ly directories and use this
functionality where appropriate.
ly:parse-string-expressi
Hi David,
This is so cool! and smart.
http://codereview.appspot.com/4974046/diff/1/scm/parser-ly-from-scheme.scm
File scm/parser-ly-from-scheme.scm (right):
http://codereview.appspot.com/4974046/diff/1/scm/parser-ly-from-scheme.scm#newcode36
scm/parser-ly-from-scheme.scm:36: (ly:parser-lookup
