On Fri, Jul 29, 2011 at 11:36:38PM +0100, Neil Puttock wrote:
On 29 July 2011 17:20, Graham Percival gra...@percival-music.ca wrote:
Could somebody get rid of these already? They're left-over from
Valentin's note name changes from Dec 2010 or so;
They come from parsing
Am Donnerstag 28 Juli 2011, 08:25:25 schrieb Jan Nieuwenhuizen:
Graham Percival writes:
You mean, like
23cdda9506931d5b9a1e75ee8be8b74f9084a7c0
?
Yes (I would have called the option --log).
I'd call it 20% rather than 90%, but yes, Phil's work on
lilypond-book will
2011/7/29 Reinhold Kainhofer reinh...@kainhofer.com:
The other thing is that all commands called by make are echoed on the console,
always including several lines of include pathes. While this might sound
useful, in fact it isn't because the exact command does not help you. make
seems to set
- Original Message -
From: Reinhold Kainhofer reinh...@kainhofer.com
To: lilypond-devel@gnu.org
Sent: Friday, July 29, 2011 11:30 AM
Subject: Re: GOP-PROP 5: build system output (probable 2?)
Am Donnerstag 28 Juli 2011, 08:25:25 schrieb Jan Nieuwenhuizen:
Graham Percival writes:
You
- Original Message -
From: Francisco Vila paconet@gmail.com
To: Reinhold Kainhofer reinh...@kainhofer.com
Cc: lilypond-devel@gnu.org
Sent: Friday, July 29, 2011 11:45 AM
Subject: Re: GOP-PROP 5: build system output (probable 2?)
2011/7/29 Reinhold Kainhofer reinh...@kainhofer.com
Am Freitag, 29. Juli 2011, 12:55:09 schrieb Phil Holmes:
- Original Message -
Currently, the doc build is calling lilypond in verbose mode, creating
thousands of unnecessary lines like
Reinhold - I've been looking at the build system in some depth and am very
well aware of this.
- Original Message -
From: Reinhold Kainhofer reinh...@kainhofer.com
To: Phil Holmes m...@philholmes.net
Cc: lilypond-devel@gnu.org
Sent: Friday, July 29, 2011 4:46 PM
Subject: Re: GOP-PROP 5: build system output (probable 2?)
Am Freitag, 29. Juli 2011, 12:55:09 schrieb Phil Holmes
On Fri, Jul 29, 2011 at 12:30:24PM +0200, Reinhold Kainhofer wrote:
[/home/reinhold/lilypond/out/share/lilypond/current/ly/string-tunings-
init.ly
Using `nederlands' note names...
[string]
...
[string]
Could somebody get rid of these already? They're left-over from
Valentin's note name
Am Freitag, 29. Juli 2011, 18:05:40 schrieben Sie:
- Original Message -
From: Reinhold Kainhofer reinh...@kainhofer.com
However, I have failed and still fail to see where the lilypond internals
printed with --verbose can be helpful in any way during the docs build.
Those
verbose
However, I have failed and still fail to see where the lilypond
internals printed with --verbose can be helpful in any way during
the docs build. Those verbose debug messages are useful for
debugging a lilypond bug.
Yep.
However, in the docs build, we are not interested in how lilypond
Am Freitag, 29. Juli 2011, 18:56:36 schrieben Sie:
However, in the docs build, we are not interested in how lilypond
works internally, but rather where a doc build fails due to bad
input in a .ly or .tely file.
I suggest a different route: Normally, after an error message has been
- Original Message -
From: Reinhold Kainhofer reinh...@kainhofer.com
To: Werner LEMBERG w...@gnu.org; lilypond-devel@gnu.org
Sent: Friday, July 29, 2011 6:31 PM
Subject: Re: GOP-PROP 5: build system output (probable 2?)
Am Freitag, 29. Juli 2011, 18:56:36 schrieben Sie:
However
On Fri, Jul 29, 2011 at 06:38:53PM +0100, Phil Holmes wrote:
- Original Message - From: Reinhold Kainhofer
reinh...@kainhofer.com
Yes, that would be *extremely* helpful (not only for the lilypond
documentation, but also to other lilypond-book users). The only
question is:
who will
On 29 July 2011 17:20, Graham Percival gra...@percival-music.ca wrote:
Could somebody get rid of these already? They're left-over from
Valentin's note name changes from Dec 2010 or so;
They come from parsing string-tunings-init.ly.
they were
debugging messages which were supposed to be
Sorry, this reply went only to Graham by accident. Here it is for lilypond-
devel:
-- Weitergeleitete Nachricht --
Betreff: Re: GOP-PROP 5: build system output (probable 2?)
Datum: Freitag, 29. Juli 2011, 23:07:11
Von: Reinhold Kainhofer reinh...@kainhofer.com
An: Graham
Am Samstag, 30. Juli 2011, 00:42:58 schrieb Reinhold Kainhofer:
Am Freitag, 29. Juli 2011, 18:20:25 schrieben Sie:
On Fri, Jul 29, 2011 at 12:30:24PM +0200, Reinhold Kainhofer wrote:
[/home/reinhold/lilypond/out/share/lilypond/current/ly/string-tunings
-
init.ly
Using
Graham Percival writes:
You mean, like
23cdda9506931d5b9a1e75ee8be8b74f9084a7c0
?
Yes (I would have called the option --log).
I'd call it 20% rather than 90%, but yes, Phil's work on
lilypond-book will certainly be valuable!
Assuming that --redirect-lilypond-output is used during build
Graham Percival writes:
You mean, like
23cdda9506931d5b9a1e75ee8be8b74f9084a7c0
?
Yes (I would have called the option --log).
I'd call it 20% rather than 90%, but yes, Phil's work on
lilypond-book will certainly be valuable!
Assuming that --redirect-lilypond-output is used during build
On Thu, Jul 28, 2011 at 08:25:25AM +0200, Jan Nieuwenhuizen wrote:
Graham Percival writes:
You mean, like
23cdda9506931d5b9a1e75ee8be8b74f9084a7c0
?
Yes (I would have called the option --log).
IMO a long descriptive name is better than a short name that's
open to interpretation.
I still don't feel that we have any kind of consensus on this.
Here's an updated proposal.
http://lilypond.org/~graham/gop/gop_5.html
** Proposal summary
When you run make or make doc,
* All output will be saved to various log files, with the
exception of output directly from
Graham Percival writes:
I still don't feel that we have any kind of consensus on this.
Here's an updated proposal.
Ah, great.
So what if we add a --log option to lilypond-book (and probably
to lilypond), that [always in verbose mode?] writes individual
.log files alongside the output. Would
On Thu, Jul 28, 2011 at 07:33:04AM +0200, Jan Nieuwenhuizen wrote:
Graham Percival writes:
I still don't feel that we have any kind of consensus on this.
Here's an updated proposal.
So what if we add a --log option to lilypond-book (and probably
to lilypond), that [always in verbose
22 matches
Mail list logo
