Re: testing 2.13.7, bumped fontforge+double

2009-11-05 Thread Jan Nieuwenhuizen
Op donderdag 05-11-2009 om 22:23 uur [tijdzone +], schreef Graham Percival: > On Thu, Nov 05, 2009 at 10:36:41PM +0100, Jan Nieuwenhuizen wrote: > > Op donderdag 05-11-2009 om 17:27 uur [tijdzone +], schreef Graham > > Percival: > Jan, since you know both python and GUB, could you try maki

Re: Issue 872 in lilypond: Changes split-page has broken images

2009-11-05 Thread Jan Nieuwenhuizen
Op donderdag 05-11-2009 om 22:40 uur [tijdzone +], schreef Graham Percival: > On Thu, Nov 05, 2009 at 07:56:11PM +0100, John Mandereau wrote: > > Le jeudi 05 novembre 2009 à 00:30 +, Graham Percival a écrit : > I thought that Jan was complaining about the "general" name. I thought that it

Re: [PATCH] [doc] New paper margin handling

2009-11-05 Thread Neil Puttock
2009/10/30 Michael Käppler : > Better now? LGTM, applied. Thanks, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc build failure: pngtopnm: Error writing single byte sample to file

2009-11-05 Thread Graham Percival
Please keep emails on the mailist. On Fri, Nov 06, 2009 at 12:22:57AM +0100, Harmath Dénes wrote: > On 2009.11.05., at 23:02, Graham Percival wrote: >> That all looks typical. IIRC in gub we use freetype 2.3.11, but >> that was to workaround an OSX 10.6 bug, so it shouldn't affect >> you. > > Hm

Re: New twoside mode.

2009-11-05 Thread Neil Puttock
2009/11/5 Patrick McCarty : > The rumors are true.  :-) Ha! I knew it; the superiority of emacs is confirmed. ;) Actually, emacs also fails to indent properly in some situations; there's a particularly annoying example in music-functions-init.ly, where a parenthesis in a docstring breaks indenta

Re: New twoside mode.

2009-11-05 Thread Neil Puttock
2009/11/5 Michael Käppler : > I've removed the hard tabs now. I remember the discussion some time ago on > -devel "spaces vs. tabs" which I was confused about. > I don't think there was a clear result: so am I allowed to never use hard > tabs but spaces in the future? I think hard tabs are fine,

Re: testing 2.13.7, bumped fontforge+double

2009-11-05 Thread Neil Puttock
2009/11/5 Graham Percival : > Oops, did I forget to push?  I remember committing the change at > university.  Go ahead and do it. OK, done. Thanks, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lily

Re: length of staff lines in score with only spacer notes

2009-11-05 Thread Neil Puttock
2009/11/5 Reinhold Kainhofer : > If I have a score containing only an s8 spacer rest, the staff lines will > always have the same length, no matter how wide the key/clef/time signatures > are. As a consequence, in some cases the staff lines are way too short > (leaving > to the time signature with

Re: testing 2.13.7, bumped fontforge+double

2009-11-05 Thread Graham Percival
On Thu, Nov 05, 2009 at 10:47:59PM +, Neil Puttock wrote: > 2009/11/5 Graham Percival : > > > Awesome!  I'll make a test 2.13.8 tomorrow... I want to test some > > new regtest-handling code anyway.  But I'll wait at least until > > Monday before making an official release. > > If it's OK, I'd

realtime development with IRC

2009-11-05 Thread Graham Percival
In the midst of all the wailing and gnashing of teeth, and before I go drink myself into a stupor for screwing up yet another release (the 2.13.7 online docs are borked, although the local offline docs look just peachy), I'd like to add a positive note. Jan and I have been collaborating on GUB for

Re: testing 2.13.7, bumped fontforge+double

2009-11-05 Thread Neil Puttock
2009/11/5 Graham Percival : > Awesome!  I'll make a test 2.13.8 tomorrow... I want to test some > new regtest-handling code anyway.  But I'll wait at least until > Monday before making an official release. If it's OK, I'd like to bump the version now, so I can apply Michael's two-sided margins pa

Re: Issue 872 in lilypond: Changes split-page has broken images

2009-11-05 Thread Graham Percival
On Thu, Nov 05, 2009 at 08:13:03PM +0100, John Mandereau wrote: > Le jeudi 05 novembre 2009 à 18:28 +, Graham Percival a écrit : > > Sure we can, with symlinks. "make doc" would produce out-www/ and > > out-www/doc-v2.13/ with a symlink from doc-v2.13/ to doc/. Stuff in > > out-www/*.html poi

Re: Issue 872 in lilypond: Changes split-page has broken images

2009-11-05 Thread Graham Percival
On Thu, Nov 05, 2009 at 07:56:11PM +0100, John Mandereau wrote: > Le jeudi 05 novembre 2009 à 00:30 +, Graham Percival a écrit : > > It seems to work. I had to change all the @ref{} in the text, but > > it looks fine now. > > Barring well-argumented opposition, I'm going to revert this and ap

Re: testing 2.13.7, bumped fontforge+double

2009-11-05 Thread Graham Percival
On Thu, Nov 05, 2009 at 10:36:41PM +0100, Jan Nieuwenhuizen wrote: > Op donderdag 05-11-2009 om 17:27 uur [tijdzone +], schreef Graham > Percival: > > Sure, sounds reasonable. If anybody feels like looking into this, go > > ahead. If not, please add it to the tracker, because I won't remember

Re: Doc build failure: pngtopnm: Error writing single byte sample to file

2009-11-05 Thread Graham Percival
On Thu, Nov 05, 2009 at 10:53:55PM +0100, Harmath Dénes wrote: > On 2009.11.05., at 18:06, Graham Percival wrote: > >> BTW, are you on OSX 10.5 or 10.6? > > My software environment: That all looks typical. IIRC in gub we use freetype 2.3.11, but that was to workaround an OSX 10.6 bug, so it shoul

Re: Doc build failure: pngtopnm: Error writing single byte sample to file

2009-11-05 Thread Harmath Dénes
On 2009.11.05., at 18:06, Graham Percival wrote: 2009/11/5 Harmath Dénes : You were right. I finally managed to put the scripts' location before /opt/local/bin in my path, and now it proceeds. But after a while, I get the following error: Pango-ERROR **: Unable to open font file /Library/Fo

Re: testing 2.13.7, bumped fontforge+double

2009-11-05 Thread Jan Nieuwenhuizen
Op donderdag 05-11-2009 om 17:27 uur [tijdzone +], schreef Graham Percival: > On Thu, Nov 5, 2009 at 5:20 PM, Trevor Daniels wrote: > > > > Mats Bengtsson wrote Thursday, November 05, 2009 12:59 PM > Sure, sounds reasonable. If anybody feels like looking into this, go > ahead. If not, pleas

Re: Issue 872 in lilypond: Changes split-page has broken images

2009-11-05 Thread John Mandereau
Le jeudi 05 novembre 2009 à 18:28 +, Graham Percival a écrit : > Is that a firm rule, or just a suggestion? Node names are used like titles in Info, so unless if there's a good reason (e.g. the node name is a program name), it should start with a capital, shouldn't it? > Sure we can, with sy

Re: Issue 872 in lilypond: Changes split-page has broken images

2009-11-05 Thread John Mandereau
Le jeudi 05 novembre 2009 à 00:30 +, Graham Percival a écrit : > It seems to work. I had to change all the @ref{} in the text, but > it looks fine now. Barring well-argumented opposition, I'm going to revert this and apply the patch below, as completely downcasing titles — node names are some