Re: Changing snippets in the documentation
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 helpful. If there are helpful lines in the output, they would be likely to show up somewhere above, where snippets are extracted from the .itely files. The old snippets were in the translations; running update-snippets.py copied the syntax changes over from user. Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Changing snippets in the documentation
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 cached in out-www/ but in out/lybook-db, which is well cleaned by make web-clean. FYI rm -rf out-www only cleans the result of WWW-post target. Cheers, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Changing snippets in the documentation
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 rebuilt in this case. However, if you change only a selected snippet in input/lsr, the user manuals won't be rebuilt. Instead of deleting files by hand, I recommend to touch files to force rebuilding, see Building Documentation in Application Usage for more details. For example, deleting all of out-www , Documentation/out-www and Documentation/user/out-www would suffice or it would be excessive? Deleting Documentation/out-www should be enough. Cheers, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Changing snippets in the documentation
On 12/14/08 2:13 PM, John Mandereau john.mander...@gmail.com 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 uptodate. Nothing, all what should be rebuilt is actually rebuilt in this case. However, if you change only a selected snippet in input/lsr, the user manuals won't be rebuilt. Instead of deleting files by hand, I recommend to touch files to force rebuilding, see Building Documentation in Application Usage for more details. I'm sorry, but I didn't explain myself clearly. It's not the selected snippets that I've changed, but a snippet actually in the manual. As part of the lybook processing, it strips out the snippets, and then they're each processed individually, at least as far as I can determine. 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-strings.itely and has not been changed. I can't figure out why. Carl Sorensen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Changing snippets in the documentation
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-strings.itely and has not been changed. I can't figure out why. I can't either... unless you post the last lines of make web output. It would be nice if you could also report whether a clean build of the same Git revision works for you. Cheers, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Changing snippets in the documentation
On 12/14/08 6:01 PM, John Mandereau john.mander...@gmail.com 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 stops on a snippet that has been extracted from fretted-strings.itely and has not been changed. I can't figure out why. I can't either... unless you post the last lines of make web output. 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 helpful. If there are helpful lines in the output, they would be likely to show up somewhere above, where snippets are extracted from the .itely files. It would be nice if you could also report whether a clean build of the same Git revision works for you. OK, I'll try the clean build. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Changing snippets in the documentation
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 was wrong in the lybook-db file. How are the snippets extracted from the documentation, and what is necessary to clean them up? 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. :) Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Changing snippets in the documentation
On 12/13/08 8:13 AM, Graham Percival gra...@percival-music.ca 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, and the snippet was correct in the .itely file, but it was wrong in the lybook-db file. How are the snippets extracted from the documentation, and what is necessary to clean them up? 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. :) Actually, I tried it and it didn't work. I get a clean build when I run make web in Documentation/user, but when I try to build from the main directory, it fails. Am I OK to push if make web succeeds in Documentation/user, but not in the top directory? Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
