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 I'm
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"
; "Francisco Vila" <[EMAIL PROTECTED]>;
"Jonathan Kulp" <[EMAIL PR
-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 uploa
-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 gi
-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 y
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-tas
-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 a
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 acc
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?
http://codereview.appspot.com/5073/di
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 f
> 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 a
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 t
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, th
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
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 br
-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 ques
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 s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 12. September 2008 schrieb Patrick McCarty:
> My latest doc changes were pushed 27 hours, but I can't see the
> changes on your server
Ah, yes, the Spanish docs had one spurious @end itemize, where the list was
moved to a different secti
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
http://git
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
>> > modifica
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 f
> Andrew, feel free to suggest a new color for the footer :-)
>
> Cheers,
> John
You could change the footer from #e8ffe8 to #e7efe3 and the border
from #c0ffc0 to #ccd3cc. It looks like the padding/spacing in the
footer could be improved but for now I'm more curious to see Patrick's
design (and o
-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 -dev
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 t
> Anyway, here finally is a series of patches implementing these
> accidentals.
This looks very nice!
> Anyone up for a review?
Here my comments, after applying all six patches locally.
. With patch #6, you are widening the shape of a sharp if you either
attach an up arrow or two arrows,
30 matches
Mail list logo
