On Thu, 2010-02-18 at 13:46 -0700, Carl Sorensen wrote:
>
>
> On 2/18/10 11:58 AM, "Joe Neeman" wrote:
>
> > On Thu, 2010-02-18 at 10:56 -0700, Carl Sorensen wrote:
> >
> > You need to be running a lilypond binary that was compiled with
> > --enable-debugging for it to work.
>
> I've been doi
On 2/18/10 11:58 AM, "Joe Neeman" wrote:
> On Thu, 2010-02-18 at 10:56 -0700, Carl Sorensen wrote:
>
> You need to be running a lilypond binary that was compiled with
> --enable-debugging for it to work.
I've been doing that., but thanks for the tip.
> Also, the regtest doesn't produce
> a
On Thu, 2010-02-18 at 10:56 -0700, Carl Sorensen wrote:
>
>
> On 2/17/10 4:53 PM, "Joe Neeman" wrote:
>
> >
> > I don't really make use of it anymore, since I've become familiar enough
> > with the source that it isn't really useful. But it should still work
> > (there is a regression test, gr
On Wed, Feb 17, 2010 at 11:21 PM, Carl Sorensen wrote:
> I stumbled across your "Life of a Grob" feature while I was looking up stuff
> on Figured Bass.
>
> <http://lists.gnu.org/archive/html/lilypond-devel/2006-09/msg00069.html>
That would be a nice feature story f
On Wed, 2010-02-17 at 15:21 -0700, Carl Sorensen wrote:
> Joe,
>
> I stumbled across your "Life of a Grob" feature while I was looking up stuff
> on Figured Bass.
>
> <http://lists.gnu.org/archive/html/lilypond-devel/2006-09/msg00069.html>
>
> I think th
Joe,
I stumbled across your "Life of a Grob" feature while I was looking up stuff
on Figured Bass.
<http://lists.gnu.org/archive/html/lilypond-devel/2006-09/msg00069.html>
I think this would be really good to add to either the CG or the Extending
LilyPond manual.
Can you
On Sat, 2006-09-23 at 13:47 +0200, Han-Wen Nienhuys wrote:
> Joe Neeman wrote:
> > On Sat, 2006-09-16 at 16:29 +0200, Han-Wen Nienhuys wrote:
> >> Joe Neeman wrote:
> >>> Understanding the LilyPond source often boils down to figuring out what
> >>> is happening to the Grobs. Where (and why) are the
Joe Neeman wrote:
On Sat, 2006-09-16 at 16:29 +0200, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
Understanding the LilyPond source often boils down to figuring out what
is happening to the Grobs. Where (and why) are they being created,
modified and destroyed? I've spent many hours tracing Lily th
On Sat, 2006-09-16 at 16:29 +0200, Han-Wen Nienhuys wrote:
> Joe Neeman wrote:
> > Understanding the LilyPond source often boils down to figuring out what
> > is happening to the Grobs. Where (and why) are they being created,
> > modified and destroyed? I've spent many hours tracing Lily through a
On Sun, 2006-09-17 at 20:35 +0200, Ruud van Silfhout wrote:
> >> I don't suppose you'd know how to do this in graphviz? I'm quite new to
> >> it.
> >>
> Hi,
>
> Adding a label to a node is done by adding an extra line in the dot-file
> containing the name of the node followed by [label="1: y
I don't suppose you'd know how to do this in graphviz? I'm quite new to
it.
Hi,
Adding a label to a node is done by adding an extra line in the dot-file
containing the name of the node followed by [label="1: yourlabeltext"];
so for a node with name x this would be: x [label="1: yourlabe
> > Very nice! A minor suggestion: Please add a counter to the boxes so
> > that they are enumerated. Then the start of an arrow should be
> > labeled with the number of the target box, and the end of an arrow
> > should tagged with the number of the origin box.
>
> I don't suppose you'd know ho
On Sun, 2006-09-17 at 01:20 +0200, Han-Wen Nienhuys wrote:
> Joe Neeman wrote:
> > On Sat, 2006-09-16 at 16:29 +0200, Han-Wen Nienhuys wrote:
> >> Some comments:
> >>
> >> * can you add another macro layer, so __LINE__ and __FILE__ aren't
> >> sprinkled around in the code? For good measure, you co
Joe Neeman wrote:
On Sat, 2006-09-16 at 16:29 +0200, Han-Wen Nienhuys wrote:
Some comments:
* can you add another macro layer, so __LINE__ and __FILE__ aren't
sprinkled around in the code? For good measure, you could also add
__FUNCTION__ .
How about something like the attached patch? I "ove
On Sat, 2006-09-16 at 20:47 +0200, Werner LEMBERG wrote:
> > The file test.ly produces a
> > graphviz output file, "graph.dot", that lets you visualise the changes
> > in Grobs throughout LilyPond execution. For now, you'll need to add a
> > closing brace to the end of graph.dot.
>
> Very nice! A
On Sat, 2006-09-16 at 16:29 +0200, Han-Wen Nienhuys wrote:
> Some comments:
>
> * can you add another macro layer, so __LINE__ and __FILE__ aren't
> sprinkled around in the code? For good measure, you could also add
> __FUNCTION__ .
How about something like the attached patch? I "overload" get_p
> The file test.ly produces a
> graphviz output file, "graph.dot", that lets you visualise the changes
> in Grobs throughout LilyPond execution. For now, you'll need to add a
> closing brace to the end of graph.dot.
Very nice! A minor suggestion: Please add a counter to the boxes so
that they ar
Joe Neeman wrote:
Understanding the LilyPond source often boils down to figuring out what
is happening to the Grobs. Where (and why) are they being created,
modified and destroyed? I've spent many hours tracing Lily through a
debugger and it is mind-blowingly tedious.
So I quickly hacked a few t
Understanding the LilyPond source often boils down to figuring out what
is happening to the Grobs. Where (and why) are they being created,
modified and destroyed? I've spent many hours tracing Lily through a
debugger and it is mind-blowingly tedious.
So I quickly hacked a few things together and c
19 matches
Mail list logo
