Re: Changing snippets in the documentation

2008-12-15 Thread Neil Puttock
Hi Carl, > The make web choked on trying to run a lilypond snippet. I looked at the > snippet, and the reason that lilypond choked was because the snippet was the > *old* version of the snippet, not the new version of the snippet. So the > last lines of the make web output aren't likely to be he

Re: Changing snippets in the documentation

2008-12-14 Thread Carl D. Sorensen
On 12/14/08 6:01 PM, "John Mandereau" wrote: > Le dimanche 14 décembre 2008 à 17:41 -0700, Carl D. Sorensen a écrit : >> I changed a snipped that is in fretted-strings.itely. When I run make web >> in Documentation/user, everything works fine. When I run make web from ., >> the process stop

Re: Changing snippets in the documentation

2008-12-14 Thread John Mandereau
Le dimanche 14 décembre 2008 à 17:41 -0700, Carl D. Sorensen a écrit : > I changed a snipped that is in fretted-strings.itely. When I run make web > in Documentation/user, everything works fine. When I run make web from ., > the process stops on a snippet that has been extracted from > fretted-s

Re: Changing snippets in the documentation

2008-12-14 Thread Carl D. Sorensen
On 12/14/08 2:13 PM, "John Mandereau" wrote: > Le dimanche 14 décembre 2008 à 21:30 +0100, Francisco Vila a écrit : >> It would be very useful to know exactly what files have to be deleted >> if you e.g. modify a single user/*itely file, to be sure that the >> final output in out-www is uptoda

Re: Changing snippets in the documentation

2008-12-14 Thread John Mandereau
Le dimanche 14 décembre 2008 à 21:30 +0100, Francisco Vila a écrit : > It would be very useful to know exactly what files have to be deleted > if you e.g. modify a single user/*itely file, to be sure that the > final output in out-www is uptodate. Nothing, all what should be rebuilt is actually re

Re: Changing snippets in the documentation

2008-12-14 Thread Francisco Vila
2008/12/14 John Mandereau : > Le samedi 13 décembre 2008 à 07:13 -0800, Graham Percival a écrit : >> I used >> rm -rf out-www/ >> >> It's not the ideal solution, since you have to wait for 20 minutes >> to compile the entire docs again, but it works. :) > > This is even little of a real solution

Re: Changing snippets in the documentation

2008-12-14 Thread John Mandereau
Le samedi 13 décembre 2008 à 07:13 -0800, Graham Percival a écrit : > I used > rm -rf out-www/ > > It's not the ideal solution, since you have to wait for 20 minutes > to compile the entire docs again, but it works. :) This is even little of a real solution: lilypond-book snippets are not cach

Re: Changing snippets in the documentation

2008-12-13 Thread Carl D. Sorensen
On 12/13/08 8:13 AM, "Graham Percival" wrote: > On Sat, Dec 13, 2008 at 07:51:45AM -0700, Carl D. Sorensen wrote: >> It failed on a snippet that was extracted from the manual. When I looked at >> the snippet, it was the old version, not the new version. I checked the >> .itely file again, an

Re: Changing snippets in the documentation

2008-12-13 Thread Graham Percival
On Sat, Dec 13, 2008 at 07:51:45AM -0700, Carl D. Sorensen wrote: > It failed on a snippet that was extracted from the manual. When I looked at > the snippet, it was the old version, not the new version. I checked the > .itely file again, and the snippet was correct in the .itely file, but it > w

Changing snippets in the documentation

2008-12-13 Thread Carl D. Sorensen
I have made a change to predefined fretboards that requires a change syntax for the user. I changed the snippets in the documentation to reflect the new syntax. As a final check, I tried make web. It failed on a snippet that was extracted from the manual. When I looked at the snippet, it was th