Good work! A few comments below.
http://codereview.appspot.com/4609041/diff/12001/scm/define-grobs.scm
File scm/define-grobs.scm (right):
http://codereview.appspot.com/4609041/diff/12001/scm/define-grobs.scm#newcode141
scm/define-grobs.scm:141: (woot . 1)
This seems like 1337 $p34k - I have ne
Hello
From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
[lilypond-devel-bounces+james.lowe=datacore@gnu.org] on behalf of Carl
Sorensen [c_soren...@byu.edu]
Sent: 17 June 2011 00:25
To: lemniskata.bernoull...@gmail.com; tdanielsmu...@googlem
Am 16.06.2011 23:19, schrieb Carl Sorensen:
On 6/16/11 2:57 PM, "Janek Warchoł"
wrote:
2011/6/14 Marc Hohl:
Am 13.06.2011 22:16, schrieb Janek Warchoł:
2011/6/13 Janek Warchoł:
Bad news: it doesn't work (the flags are squashed)
An idea came to my mind - maybe we can use our *.table files
Carl et al,
From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
[lilypond-devel-bounces+james.lowe=datacore@gnu.org] on behalf of Carl
Sorensen [c_soren...@byu.edu]
Sent: 17 June 2011 02:05
To: Aleksandr Andreev
Cc: lilypond-devel@gnu.org
Subj
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc: "Graham Percival" ;
Sent: Thursday, June 16, 2011 9:27 PM
Subject: Re: Patch: small reduction in output from make doc
"Phil Holmes" writes:
TBH, I don't agree at all. I personally think there's nothing worse
than a
- Original Message -
From: "David Kastrup"
I would not mind if Lilypond wrote, upon encountering an error, all
locators that are in the input tree concerning the error. Let it be a
dozen. Those are relevant to the error. Easier to sift through them
than two thousand lines not relevan
"Phil Holmes" writes:
> From: "David Kastrup"
>> Lilypond is commonly is called from a Makefile and other utilities,
>> obliterating all useful output from them.
>>
>> The normal behavior for a Unix utility is to write to stderr when
>> something goes wrong and then bottom out with a non-zero ex
I realise I may be on thin ice here...
As many will know, I'm trying to reduce the clutter that appears on screen
as lily's build progresses. A key way of doing this is by redirecting
output to log files. If you've recently done a make doc and look in
build/out/lybook-db you'll see some of t
On Tue, Jun 14, 2011 at 9:40 PM, m...@apollinemike.com <
m...@apollinemike.com> wrote:
> Hey all,
>
> I see that the line-spanner print function looks for something that is
> called anchor-alignment (git blame insinuates that it was Joe who added
> this). This alignment, so far as I can see, is u
On Fri, Jun 17, 2011 at 09:34:38AM +0100, Phil Holmes wrote:
> I'm now thinking it would actually be better to gather all the
> output from make in a single directory, something like
> build/makelogs. That way, you'd only need to look in one place for
> any failing logged output, and it would prob
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc:
Sent: Friday, June 17, 2011 11:41 AM
Subject: Re: Logfiles from build
On Fri, Jun 17, 2011 at 09:34:38AM +0100, Phil Holmes wrote:
I'm now thinking it would actually be better to gather all the
output from make in a
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc:
Sent: Friday, June 17, 2011 11:41 AM
Subject: Re: Logfiles from build
On Fri, Jun 17, 2011 at 09:34:38AM +0100, Phil Holmes wrote:
I'm now thinking it would actually be better to gather all the
output from make in a
On Fri, Jun 17, 2011 at 10:28:37AM +0200, David Kastrup wrote:
> "Phil Holmes" writes:
>
> > From: "David Kastrup"
> >> The normal behavior for a Unix utility is to write to stderr when
> >> something goes wrong and then bottom out with a non-zero exit status.
> >> Make (or similar tools) stop,
On 11-06-17 02:34 AM, Phil Holmes wrote:
I realise I may be on thin ice here...
As many will know, I'm trying to reduce the clutter that appears on
screen as lily's build progresses. A key way of doing this is by
redirecting output to log files. If you've recently done a make doc
and look i
On Fri, Jun 17, 2011 at 04:19:33PM +0100, Graham Percival wrote:
> In keeping with the GOP mentor discussion, (proposal summary)
> http://lilypond.org/~graham/gop/gop_2.html
> I feel compelled to warn you that you do not have "a realistic
> expectation of how things will work". I hate to say it, b
On Fri, Jun 17, 2011 at 11:53:15AM +0100, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
>
>
> >On Fri, Jun 17, 2011 at 09:34:38AM +0100, Phil Holmes wrote:
> >Before any work is done on the central log/ or
> >build-log/ directory, I would really like to have the capabi
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc:
Sent: Friday, June 17, 2011 4:19 PM
Subject: Re: Logfiles from build
On Fri, Jun 17, 2011 at 11:53:15AM +0100, Phil Holmes wrote:
- Original Message - From: "Graham Percival"
>On Fri, Jun 17, 2011 at 09:34
On Fri, Jun 17, 2011 at 04:35:47PM +0100, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
>
> >So when Reinhold and I say "we must not hide any errors in make",
>
> In that case, I can't see that anything I can do can prevent these
> being visible. The only thing I can
On Wed, Jun 15, 2011 at 04:31:21PM +0100, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
>
> >Hmm. Does it only create key-initial.midi, or does it also create
> >key-initial.pdf ? (or .eps, or .png, etc)
>
> According to the output, it also creates *.pdf. However, n
- Original Message -
From: "Graham Percival"
[snip]
with my memory of recent discussions, I know to look in
/home/gperciva/src/lilypond/build/out/lybook-db/snippet-names--25272072.log
for hints, but that's not at all obvious from just looking at the
command-line output. Inside that fil
James wrote:
> It's crude (but effective), you either sym link the font dirs to point to the
> Gonville stuff (which is supplied via a zip/tgz file that you extract in
> situ) or as in the case of windows and mac you rename the old font dir and
> move the goneville one in its place.
>
This sou
Hello,
)-Original Message-
)From: Aleksandr Andreev [mailto:aleksandr.andr...@gmail.com]
)Sent: 17 June 2011 18:02
)To: James Lowe
)Cc: lilypond-devel@gnu.org
)Subject: Re: Kievan square notation in LilyPond
)
)James wrote:
)
)> It's crude (but effective), you either sym link the font dirs
On Fri, Jun 17, 2011 at 06:32:22PM +0100, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
>
> >with my memory of recent discussions, I know to look in
> >/home/gperciva/src/lilypond/build/out/lybook-db/snippet-names--25272072.log
>
> This kind of issue prompted my sugges
On 17/06/2011 2:11 PM, Graham Percival wrote:
On Fri, Jun 17, 2011 at 06:32:22PM +0100, Phil Holmes wrote:
- Original Message - From: "Graham Percival"
with my memory of recent discussions, I know to look in
/home/gperciva/src/lilypond/build/out/lybook-db/snippet-names--25272072.log
On Fri, Jun 17, 2011 at 02:18:55PM -0400, Julien Rioux wrote:
> On 17/06/2011 2:11 PM, Graham Percival wrote:
> >Again, on the shell, it would be something like this:
> > make ...blah... || echo "build failed" && tail logfile
> >but there might be a nicer way to do it.
>
> but then when blah fail
On Fri, Jun 17, 2011 at 07:35:19PM +0100, Graham Percival wrote:
> On Fri, Jun 17, 2011 at 02:18:55PM -0400, Julien Rioux wrote:
> > On 17/06/2011 2:11 PM, Graham Percival wrote:
> > > make ...blah... || echo "build failed" && tail logfile
> >
> > but then when blah fails, make will not stop, sin
On Fri, Jun 17, 2011 at 07:35:19PM +0100, Graham Percival wrote:
> > >Again, on the shell, it would be something like this:
> > > make ...blah... || echo "build failed" && tail logfile
> > >but there might be a nicer way to do it.
> >
> > but then when blah fails, make will not stop, since the re
Graham Percival writes:
> On Fri, Jun 17, 2011 at 02:18:55PM -0400, Julien Rioux wrote:
>> On 17/06/2011 2:11 PM, Graham Percival wrote:
>> >Again, on the shell, it would be something like this:
>> > make ...blah... || echo "build failed" && tail logfile
>> >but there might be a nicer way to do
On Fri, Jun 17, 2011 at 10:06:01PM +0200, Matthias Kilian wrote:
> Just wait a few days until I've some spare time available to help
> you with this, will you?
Certainly! Thank you for your interest; I know that you know far
more than me about this.
Please also take a look at two recent git comm
On 17/06/2011 3:10 PM, Graham Percival wrote:
On Fri, Jun 17, 2011 at 07:35:19PM +0100, Graham Percival wrote:
On Fri, Jun 17, 2011 at 02:18:55PM -0400, Julien Rioux wrote:
On 17/06/2011 2:11 PM, Graham Percival wrote:
make ...blah... || echo "build failed"&& tail logfile
but then when bl
On Wed, Jun 15, 2011 at 07:46:43AM -0600, Carl Sorensen wrote:
> This is especially tragic because the initial quality of the patch was very
> high. Karin is clearly a gifted programmer who figured out how to solve
> this problem on her own. Losing her potential contributions to LilyPond is
> a r
31 matches
Mail list logo
