Neil Puttock schrieb:
2009/11/6 Marc Hohl :
Ready to be applied?
LGTM.
I don't think these comments are necesary though:
+ %% No key in tablature!
There was already a "no accidentals" comment in it,
so for the sake of consistency, I added the others.
I added another version of
Have also looked for traling spaces in lily-library.scm
http://codereview.appspot.com/150044/diff/1/4
File ly/music-functions-init.ly (right):
http://codereview.appspot.com/150044/diff/1/4#newcode612
ly/music-functions-init.ly:612: (lambda (m) (eq? 'NoteEvent
(ly:music-property m 'name)))
On 20
Le vendredi 06 novembre 2009 à 19:43 +, Graham Percival a écrit :
> On Fri, Nov 06, 2009 at 08:14:27PM +0100, John Mandereau wrote:
> > I warmly, highly and definitely second doc/v2.xx (first value of xx will
> > be 14), which is clearer than having stable docs at toplevel or in /web,
>
> I'll
Op vrijdag 06-11-2009 om 20:17 uur [tijdzone +0100], schreef John
Mandereau:
> Le vendredi 06 novembre 2009 à 20:14 +0100, John Mandereau a écrit :
> > Le vendredi 06 novembre 2009 à 18:54 +0100, Jan Nieuwenhuizen a écrit :
> > > Op vrijdag 06-11-2009 om 17:44 uur [tijdzone +], schreef Graham
>
Le jeudi 05 novembre 2009 à 22:40 +, Graham Percival a écrit :
> oh, FFS. Your solution is so ridiculously easy.
> (yes, please revert the lower-case patches from Jan and me, and
> use yours)
On theory, my solution is good, but in practice my patch miserably
fails. In most situations where I
On 2009.11.05., at 23:02, Graham Percival wrote:
Take a look at TOPDIR/out/lybook-db/aa/lily-0a4411fa.ly. What's
in the file? Does the version number say "2.13.7" ?
What happens if you copy the file to a new location, COMMENT OUT
THE STUFF ABOVE "start cut&paste section", and run lilypond on i
On Mon, Nov 9, 2009 at 9:54 AM, Jan Nieuwenhuizen wrote:
>> My bad, I'd only veto for lilypond/org/notation.html and all other
>> non-base-website docs alike. I technically have nothing against putting
>> the base website at the root.
>
> Han-Wen?
>
> The technical reasons for using web/ and doc
On Mon, Nov 09, 2009 at 02:42:24PM +0100, Harmath Dénes wrote:
> On 2009.11.05., at 23:02, Graham Percival wrote:
>> Take a look at TOPDIR/out/lybook-db/aa/lily-0a4411fa.ly. What's
>> in the file? Does the version number say "2.13.7" ?
>>
>> What happens if you copy the file to a new location, CO
On Thu, Nov 5, 2009 at 12:48 PM, David Kastrup wrote:
>
> Hi,
>
> I was wondering what the Lilypond policies are for using SRFI, such as
> SRFI-13 for string functions. My question was triggered by looking at
> scm/lily-sort.scm (only used at document creation time) which could be
There are no
I would add: make Scheme code as portable as possible.
Han-Wen Nienhuys wrote:
On Thu, Nov 5, 2009 at 12:48 PM, David Kastrup wrote:
Hi,
I was wondering what the Lilypond policies are for using SRFI, such as
SRFI-13 for string functions. My question was triggered by looking at
scm/lily-so
If I use ly:add-option in an external lilypond package to declare a new
option, e.g.
#(ly:add-option 'incipit #t
"Whether to print an incipit with the old key / clef (if provided).
If the 'ancient-style option is set to ##t, this option has no effect.")
lilypond will always set the o
On 2009.11.09., at 15:49, Graham Percival wrote:
Not unless you have a minimal example. I also hope that you
noticed my warnings about COMMENTING OUT THE STUFF ABOVE THE "CUT
AND PASTE" SECTION.
Of course. Though only the line
\include "lilypond-book-preamble.ly"
had to be commented out.
I
"Bertalan Fodor (LilyPondTool)" writes:
>> Han-Wen Nienhuys wrote:
>>
>> On Thu, Nov 5, 2009 at 12:48 PM, David Kastrup wrote:
>>
>> I was wondering what the Lilypond policies are for using
>> SRFI, such as SRFI-13 for string functions. My question was
>> triggered b
David Kastrup wrote:
"Bertalan Fodor (LilyPondTool)" writes:
Han-Wen Nienhuys wrote:
On Thu, Nov 5, 2009 at 12:48 PM, David Kastrup wrote:
I was wondering what the Lilypond policies are for using
SRFI, such as SRFI-13 for string functions. My question was
tri
On Mon, Nov 09, 2009 at 04:28:24PM +0100, Harmath Dénes wrote:
> On 2009.11.09., at 15:49, Graham Percival wrote:
>> Not unless you have a minimal example. I also hope that you
>> noticed my warnings about COMMENTING OUT THE STUFF ABOVE THE "CUT
>> AND PASTE" SECTION.
>
> Of course. Though only th
On Mon, Nov 09, 2009 at 01:25:25PM +0100, John Mandereau wrote:
> Le jeudi 05 novembre 2009 à 22:40 +, Graham Percival a écrit :
> > oh, FFS. Your solution is so ridiculously easy.
> > (yes, please revert the lower-case patches from Jan and me, and
> > use yours)
>
> On theory, my solution is
On Mon, Nov 09, 2009 at 12:28:50PM +0100, John Mandereau wrote:
> Le vendredi 06 novembre 2009 à 19:43 +, Graham Percival a écrit :
> > On Fri, Nov 06, 2009 at 08:14:27PM +0100, John Mandereau wrote:
> > > I warmly, highly and definitely second doc/v2.xx (first value of xx will
> > > be 14), wh
Reviewers: ,
Message:
This patch fixes 786 (and 800, which I think should be labeled a dupe).
No regression tests were adversely affected, but there could possibly be
some issues with creating "empty" LyricText objects.
Description:
Fixes issue 786, "Extenders in lyrics stop prematurely if a si
Hi there,
I am new to lilypond.
I am wondering if there exists an interface like mathtex, for lilypond.
For those who don't know mathtex, it's a way of embedding rendered TeX
images directly and easily in an HTML page (and therefore in wikis, in
blogs etc), through a relatively simple CGI service.
For an individual person, lilypond-book can already process html
files, so there is nothing extra needed.
If you want to have it for a multi-user situation like a wiki,
then search for "lilypond wiki" or "mediawiki" or similar terms on
the mailist; it has been discussed before. Be warned that the
2009/11/9 :
> This patch fixes 786 (and 800, which I think should be labeled a dupe).
I can't verify #800 here; the extender's still too short.
> No regression tests were adversely affected, but there could possibly be
> some issues with creating "empty" LyricText objects.
Can you check lyric-
Le samedi 07 novembre 2009 à 19:26 +, Graham Percival a écrit :
> I've got waf buliding contributor .html and .pdf in the dev/gperciva
> branch.
Ah, you got upset enough by the old build system too :-)
> I was pleasantly surprised to discover that waf supported a
> --targets= command-line,
On Tue, Nov 10, 2009 at 01:04:11AM +0100, John Mandereau wrote:
> Le samedi 07 novembre 2009 à 19:26 +, Graham Percival a écrit :
> > I was pleasantly surprised to discover that waf supported a
> > --targets= command-line, so we can specific an individual manual to
> > build.
>
> I'm not sure
23 matches
Mail list logo
