Re: Issue #768: Chord repetition shortcut

2009-11-14 Thread nicolas . sceaux
On 2009/11/12 21:40:37, Carl wrote: Nicolas, It looks great! Thanks. I have just a couple of suggestions for changes to the documentation I've addressed your remarks concerning documentation in a new patch http://codereview.appspot.com/154056

Re: Issue #768: Chord repetition shortcut

2009-11-14 Thread Carl Sorensen
On 11/14/09 3:30 AM, "nicolas.sce...@gmail.com" wrote: > On 2009/11/12 21:40:37, Carl wrote: >> Nicolas, > >> It looks great! Thanks. > >> I have just a couple of suggestions for changes to the documentation > > I've addressed your remarks concerning documentation in a new patch > >

Re: Issue #768: Chord repetition shortcut

2009-11-14 Thread nicolas . sceaux
On 2009/11/12 21:40:37, Carl wrote: http://codereview.appspot.com/154056/diff/1/10#newcode1 ly/chord-repetition-init.ly:1: \version "2.13.8" Just a question. Why do this in a .ly file instead of in a .scm file? This initializes the parser object, and thus shall be placed in a .ly file, where

Re: new abc2ly files not distributed

2009-11-14 Thread Graham Percival
On Fri, Nov 13, 2009 at 06:17:58PM +0100, Reinhold Kainhofer wrote: > Am Freitag, 13. November 2009 15:30:21 schrieb Graham Percival: > > Trying to build GUB: > > > > file from VC not distributed: lilypond-2.13.8/make/abc-vars.make > > Hmm, I'm adding the *.abc files to the EXTRA_DIST_FILES in ab

Re: Code formatter

2009-11-14 Thread demery
>> 2) many programmers view code style in a highly personal, >> quasi-religious manner. > ... >> ...Han-Wen and Jan have different views... Foe me its a matter of blocking the whitespace to to present the code in a way that makes it easier to understand. This is not easy to do with any automated

My "make doc" is broken

2009-11-14 Thread Frédéric Bron
Since I upgraded ubuntu to 9.10, make doc does not work anymore but why? Is it because of the ubuntu upgrade or because of git pull? Here is the output: ... Renaming input to: `music-function-string-markup.ly' music-function-string-markup.ly:15:24: error: syntax error, unexpected STRING, expecting

Re: My "make doc" is broken

2009-11-14 Thread Graham Percival
On Sat, Nov 14, 2009 at 07:57:05PM +0100, Frédéric Bron wrote: > Since I upgraded ubuntu to 9.10, make doc does not work anymore but > why? Is it because of the ubuntu upgrade or because of git pull? > Here is the output: > ... > Renaming input to: `music-function-string-markup.ly' > music-function

Re: My "make doc" is broken

2009-11-14 Thread Frédéric Bron
> I hope that you did a "make clean; make" first. There was a > commit recently that did something about strings and markups, so > perhaps that's the problem. I did make dist-clean and rerun autogen.sh I have redone it again and the doc is now compiling since 1 hour so I assume it is working! Do

Re: [PATCH] serious doubts about waf

2009-11-14 Thread Graham Percival
Ok, it seems the the key was to call bld.rescan(node) after adding it. I'm off to a short conference tomorrow. I expected to have internet access, but when I mentioned it to one of the professors today, he just laughed at me. :(so if I'm not around for a few days, that's why. I'm going t

Re: My "make doc" is broken

2009-11-14 Thread Frédéric Bron
> I have redone it again and the doc is now compiling since 1 hour so I > assume it is working! Do not understand what happens. > Will see tomorrow morning if anything good happened. Well it stopped with an error before tomorrow: cd ./out-www; texi2pdf -I ./out-www -I /home/bronf/lilypond/Documen

Re: Code formatter

2009-11-14 Thread Jan Nieuwenhuizen
Op vrijdag 13-11-2009 om 17:45 uur [tijdzone +], schreef Graham Percival: > On Fri, Nov 13, 2009 at 04:59:20PM -, Trevor Daniels wrote: > > > > Chris Snyder wrote Friday, November 13, 2009 4:35 PM > >> Graham Percival wrote: > interesting. is that really the GNU style? maybe I should che

Re: anybody know apache? (dir structure of docs)

2009-11-14 Thread Jan Nieuwenhuizen
Op donderdag 12-11-2009 om 23:06 uur [tijdzone +0100], schreef Reinhold Kainhofer: > ### > > ## Rewrite all non-existing files at toplevel to the /web/ dir, so > our > ## internal structure for rsync doesn't have to be changed. > RewriteEngine on > Rewrite