LGTM
please apply.
http://codereview.appspot.com/5058/diff/11/12
File flower/include/flower-proto.hh (right):
http://codereview.appspot.com/5058/diff/11/12#newcode2
Line 2: fflower-proto.hh -- typenames in flowerlib
ff?
http://codereview.appspot.com/5058
Well, now that lilypond can compile a file in emacs, I've been looking
around, getting myself acquainted with the various options.
Apparently, the 2tex option calls lilypond as lilypond -b tex
filename.ly The version of lilypond that I have installed says that
should be -f tex (assuming
OK thanks, Andrew. I'll pass that on to Ralph
for indexing.
Are you up for more doc work?
Trevor
- Original Message -
From: Andrew Hawryluk [EMAIL PROTECTED]
To: Trevor Daniels [EMAIL PROTECTED]; lily-devel
lilypond-devel@gnu.org; Francisco Vila [EMAIL PROTECTED];
Jonathan Kulp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 12. September 2008 schrieb Evan Martin:
On Thu, Sep 11, 2008 at 1:17 PM, Reinhold Kainhofer
[EMAIL PROTECTED] wrote:
The last argument to git cl upload is passed along to git diff, so
something like
git cl upload HEAD^^ HEAD^
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 12. September 2008 schrieb [EMAIL PROTECTED]:
http://codereview.appspot.com/5073/diff/1/3#oldcode42
Line 42: 1, 0, 0, (SCM grob),
It looks as if you have the patch reversed.
Perhaps git-cl confusion?
Oops, you are right! Since git-cl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 12. September 2008 schrieb Patrick McCarty:
Hi Kieren,
On Thu, Sep 11, 2008 at 04:49:56PM -0400, Kieren MacMillan wrote:
[Lilypond 2.11.58]
I didn't realize 2.11.58 was released, since Han-Wen hasn't pushed a
tagged commit yet.
Hello all,
I'd like to be able to say, e.g.
\header
{
title = My Really Cool Composition
alternateTitle = MRCC
}
and then at some point use
\fromproperty #'header:alternateTitle
Is there any mechanism — built-in or Scheme-tastic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 12. September 2008 schrieb Kieren MacMillan:
Hello all,
I'd like to be able to say, e.g.
\header
{
title = My Really Cool Composition
alternateTitle = MRCC
}
and then at some point
Hi all,
for various reasons I've been inactive on this list for quite a long
time. My last post was concerning a possible contribution, namely
arrowed microtonal accidentals, which have been requested on this list
quite a few times.
IIRC, I had already sent a pdf file showing off the new
http://codereview.appspot.com/5073/diff/1/3
File lily/staff-symbol-referencer-scheme.cc (left):
http://codereview.appspot.com/5073/diff/1/3#oldcode42
Line 42: 1, 0, 0, (SCM grob),
It looks as if you have the patch reversed.
Perhaps git-cl confusion?
http://codereview.appspot.com/5073
http://codereview.appspot.com/5073/diff/601/403
File lily/staff-symbol-referencer-scheme.cc (right):
http://codereview.appspot.com/5073/diff/601/403#newcode41
Line 41: LY_DEFINE (ly_line_thickness, ly:line-thickness,
can you work staff-symbol in the name?
Doc Team
I've been fiddling with the Documentation Coordination page that John set up
at
http://lilypondwiki.tuxfamily.org/index.php?title=Documentation_coordination
It looks like it will be useful, but there is more to do yet. Unfortunately
I shall be away for a week from tomorrow, almost
On Fri, Sep 12, 2008 at 3:00 AM, Reinhold Kainhofer
[EMAIL PROTECTED] wrote:
I didn't realize 2.11.58 was released, since Han-Wen hasn't pushed a
tagged commit yet. :-)
It's not released, but the current development version already has the next
version number, mainly because new features
Are you up for more doc work?
Trevor
Yes, I'm up for more. I'm a slow doc writer, but I'm willing. :)
Also, I did go through the Winds section during GDP and got it all
cleaned up except the fingerings section, so you can change the not
yet started label. I expect to have something to add
Andrew Hawryluk Friday, September 12, 2008 8:27 PM
Are you up for more doc work?
Trevor
Yes, I'm up for more. I'm a slow doc writer, but I'm willing. :)
Great! What sort of work would you like? There are
a few sections that still need fairly major revision
and editing; there are some
I'd be up for some reviewing. I'm still new enough at LilyPond that
I'd learn a lot from some 'assigned readings' and I could probably
tell if they make sense to someone that doesn't compile their own
LilyPond binaries over breakfast.
Andrew
On Fri, Sep 12, 2008 at 1:43 PM, Trevor Daniels [EMAIL
Andrew Hawryluk Friday, September 12, 2008 9:02 PM
I'd be up for some reviewing. I'm still new enough at LilyPond that
I'd learn a lot from some 'assigned readings' and I could probably
tell if they make sense to someone that doesn't compile their own
LilyPond binaries over breakfast.
OK,
On 9/12/08 2:10 PM, Trevor Daniels [EMAIL PROTECTED] wrote:
Andrew Hawryluk Friday, September 12, 2008 9:02 PM
I'd be up for some reviewing. I'm still new enough at LilyPond that
I'd learn a lot from some 'assigned readings' and I could probably
tell if they make sense to someone that
On Fri, Sep 12, 2008 at 02:02:21PM -0600, Andrew Hawryluk wrote:
I'd be up for some reviewing. I'm still new enough at LilyPond that
I'd learn a lot from some 'assigned readings' and I could probably
tell if they make sense to someone that doesn't compile their own
LilyPond binaries over
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 12. September 2008 schrieb Carl D. Sorensen:
Why does a reviewer need to pull source files from git? Can't (shouldn't)
the reviewer do the final review on the docs themselves?
While I'm not in a position to answer that particular
Carl D. Sorensen Friday, September 12, 2008 9:13 PM
On 9/12/08 2:10 PM, Trevor Daniels [EMAIL PROTECTED] wrote:
Andrew Hawryluk Friday, September 12, 2008 9:02 PM
I'd be up for some reviewing. I'm still new enough at LilyPond that
I'd learn a lot from some 'assigned readings' and I could
On Fri, Sep 12, 2008 at 10:35:58PM +0200, Reinhold Kainhofer wrote:
While I'm not in a position to answer that particular question, I still want
to point out that the docs on http://kainhofer.com/~lilypond/ are
automatically built from the latest git master every morning (CEST), so these
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 12. September 2008 schrieb Stefan Thomas:
Dear James,
thanks for Your help. But what can I do, if I only want to change the size
of the bassclef and if I have an instrument like piano, where the clefs are
changing constantly?
use
Le mercredi 10 septembre 2008 à 11:49 +0200, Reinhold Kainhofer a
écrit :
Am Samstag, 6. September 2008 schrieb Andrew Hawryluk:
Here's my initial design submission for the docs - it's just a gentle
modification of the CSS file:
Cool! I applied it, and made some changes, see
On Fri, Sep 12, 2008 at 3:43 PM, John Mandereau
[EMAIL PROTECTED] wrote:
Le mercredi 10 septembre 2008 à 11:49 +0200, Reinhold Kainhofer a
écrit :
Am Samstag, 6. September 2008 schrieb Andrew Hawryluk:
Here's my initial design submission for the docs - it's just a gentle
modification of the
Sounds good. I'll read through NR 1.5 and 1.6 next week.
Andrew
On Fri, Sep 12, 2008 at 2:34 PM, Patrick McCarty [EMAIL PROTECTED] wrote:
On Fri, Sep 12, 2008 at 02:02:21PM -0600, Andrew Hawryluk wrote:
I'd be up for some reviewing. I'm still new enough at LilyPond that
I'd learn a lot from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 13. September 2008 schrieb John Mandereau:
BTW I don't know what #CCF was
supposed to mean as a color.
#rgb is the official CSS color shortcut for #rrggbb, see
http://www.w3.org/TR/CSS2/syndata.html#color-units
Actually, on -devel we
On Fri, 12 Sep 2008 16:11:20 -0700
Patrick McCarty [EMAIL PROTECTED] wrote:
Andrew has been the only one to submit a design so far, but how are we
going to decide which design to use if 10 more people submit designs?
What a horrible problem to have. :)
- find any common issues amongst the
28 matches
Mail list logo
