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
Hi,
On Sat, 23 Sep 2006, Han-Wen Nienhuys wrote:
>
> For questions concerning development, please use the mailing list.
> theoretically it's not impossible to build with VC++ , but you'll have to
> figure out how for yourself. We use GCC.
I doubt you will succeed: it _should_ be easier to build
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
Graham Percival wrote:
Hi,
What should we do about storing email addresses of bug reporters? The
CC field of the google issue tracker looks very inviting, but it only
allows google user names there. :(
So far I've given people a link to their bug, so they could bookmark
that and check it
For questions concerning development, please use the mailing list.
theoretically it's not impossible to build with VC++ , but you'll have
to figure out how for yourself. We use GCC.
Chris Hills wrote:
Hi LilyPond developers,
I came across LilyPond by chance recently. It's most
impressive.
