On Sat, Feb 28, 2009 at 05:41:21PM -0700, Carl D. Sorensen wrote: > > On 2/28/09 3:43 PM, "John Mandereau" <john.mander...@gmail.com> wrote: > > > Hi Carl, > > Carl D. Sorensen a écrit : > >> So, just for the record, I guess that the appropriate way to handle this > >> would be to: > >> > >> 1. Search through input/lsr for relevant files. > >> 2. Fix the snippet to make sure it compiles properly. > >> 3. Copy the snippet to input/new > >> 4. Delete the snippet from input/lsr > >> > > Yes, except you shouldn't do 4, and don't forget some snippets > > eventually come from LSR, not from input/new. > > We can't do anything about the snippets that come from LSR, can we? They're > for the old release, so they can't be updated, IIUC. > > I thought that was why we had input/new, to handle snippets that had changed > syntax from the currently-running LSR.
Yes. Files from input/new/ overwrite files from input/lsr/ (if they have exactly the same filename, of course). Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel