Neil Puttock writes:
> 2009/11/24 David Kastrup :
>
>> After applying http://codereview.appspot.com/160048> first,
>> indeed the following diff that throws out all the toplevel scoping
>> constructs and separate definitions of define-markup-command and
>> define-markup-list-command passes the reg
Hi,
For the past few months, I have been experiencing strange failures
when checking the regression test suite, and I have just discovered
why.
I recently posted to the ImageMagick forums:
http://www.imagemagick.org/discourse-server/viewtopic.php?f=1&t=15098
Even though this solution works fo
2009/11/24 David Kastrup :
> After applying http://codereview.appspot.com/160048> first,
> indeed the following diff that throws out all the toplevel scoping
> constructs and separate definitions of define-markup-command and
> define-markup-list-command passes the regressions tests. Furthermore,
Le mardi 24 novembre 2009 à 21:20 +, Graham Percival a écrit :
> On the 16th, I gave up and fixed this one myself. However, I
> discovered that I couldn't copy files from srcdir into the blddir
> without changing their name, which kind-of borks
> Documentation/pictures/.
I'm quite certain we
Hi Carl,
Le mardi 24 novembre 2009 à 14:15 -0700, Carl Sorensen a écrit :
> I've done a git grep for ukelele, and found the misspelling existing in de/
> es/ and fr/ notation/fretted-strings.itely. I'm happy to fix it in all of
> those, and I think I should do so.
Certainly.
> I have read the C
On Tue, Nov 24, 2009 at 09:42:05PM +0100, John Mandereau wrote:
> Le jeudi 12 novembre 2009 à 17:54 +, Graham Percival a écrit :
> > 1) if you can't duplicate the problem after checking out
> > dev/gperciva, then I'll check a third time to see if there's any
> > old version of waf floating aro
John,
It's been brought to my attention that we are using an incorrect spelling
for "ukulele". We've been using (at least in part of our documentation)
"ukelele".
I've done a git grep for ukelele, and found the misspelling existing in de/
es/ and fr/ notation/fretted-strings.itely. I'm happy to
Sorry for the delay, it often takes me a while to catch all traffic on
Lily lists when I'm back from a trip, even a few-days one.
Le jeudi 12 novembre 2009 à 17:54 +, Graham Percival a écrit :
> 1) if you can't duplicate the problem after checking out
> dev/gperciva, then I'll check a third t
Le samedi 21 novembre 2009 à 19:17 +, Graham Percival a écrit :
> Hmm. Now I'm wondering if I had a half-built doc tree, with the
> remains of Jan's "@node lower-case" stuff. I cleared out
> Docuemtnation/out-www/, but I didn't think to touch out/xref-maps.
I hope it's not needed to touch t
It would make sense to apply http://codereview.appspot.com/160048>
first and make this patch work on top of that.
There may be cases where a separate property-bind like this is useful in
called routines, and the markup commands from the mentioned patch might
make use of it for implementing #:prop
David Kastrup writes:
> Nicolas Sceaux writes:
>
>> I'd be insterested to see an implementation of a single
>> `define-markup-command' for builtin and user defined markups, where
>> user defined commands do not pollute the (lily) module, and still are
>> available across file includes.
>>
>> If
Han-Wen Nienhuys writes:
> On Mon, Nov 23, 2009 at 1:21 PM, David Kastrup wrote:
>
>>> lilypond a.ly b.ly
>>>
>>> we want to reuse the built-in definitions, without changes effected in
>>> a.ly leaking into the processing of b.ly
>>
>> Wouldn't just putting the built-in definition at public sco
http://codereview.appspot.com/160048/diff/1/5
File scm/markup.scm (right):
http://codereview.appspot.com/160048/diff/1/5#newcode74
scm/markup.scm:74: [ :category category ]
On 2009/11/24 11:01:59, Carl wrote:
Does this need to be [ #:category category ] ?
Done.
http://codereview.appspot.com/
[from -user]
Francesco Petrogalli wrote:
I have no idea where to find documentation about this programming in
"lilypond-scheme". There is a big list of scheme function in the
documentation, but I can't see any "tutorial" about using it.
Should this section "A.16 Scheme functions" also be moved
On Tue, Nov 24, 2009 at 09:46:07AM +0100, Francisco Vila wrote:
> 2009/11/23 Graham Percival :
> > Now that 2.13.8 is uploaded:
>
> http://lilypond.org/install/ still links 2.13.7.
Interesting. Anybody want to look at the old web/ branch to
figure out why make update-versions isn't working? The
carl.d.soren...@gmail.com writes:
> David,
>
> Thank you for posting this on Rietveld. It was much easier for me to
> review it.
>
> I have one documentation question (see below).
>
> I also have one patch philosophy question: should define-markup also
> have (at least) a :properties keyword adde
David Kastrup writes:
> Nicolas Sceaux writes:
>
>> Please ignore this case, it's broken. What I had in mind a bit more
>> complex, and probably does not really matter.
>>
>> The two important points to keep in mind are:
>>
>> 1) user defined commands shall not pollute the internal modules
>> Wh
Nicolas Sceaux writes:
> Please ignore this case, it's broken. What I had in mind a bit more
> complex, and probably does not really matter.
>
> The two important points to keep in mind are:
>
> 1) user defined commands shall not pollute the internal modules
> When file1.ly e.g. redefines a built
2009/11/24 David Kastrup
>
> > file3.ly:
> > myInclude =
> > #(define-music-function (parser location file) (string?)
> > #{ \include $file #}
> > (make-music 'void #t))
> >
> > \myInclude "file2.ly"
> > \markup \foo
>
Please ignore this case, it's broken. What I had in mind a
2009/11/23 Graham Percival :
> Now that 2.13.8 is uploaded:
http://lilypond.org/install/ still links 2.13.7.
Regards
--
Francisco Vila. Badajoz (Spain)
www.paconet.org
www.csmbadajoz.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://l
20 matches
Mail list logo
