On Mon, Jul 9, 2012 at 2:31 PM, Reinhold Kainhofer <reinh...@kainhofer.com> wrote: > > "-Eluze" <elu...@gmail.com> wrote in message >> >> On Sun, Jul 8, 2012 at 8:27 PM, Da Mota Sam <da.mota....@gmail.com> wrote: >>> I'm a pretty much new user of lilypond and I have an idea for a almost >>> dummy new feature: automatically attach lilypond code in pdf. >>> With pdf files it is possible to attach a file into it. >> >> the basic function in LilyPond is given with >> >> \include "test.ly" >> \markup \verbatim-file #"test.ly" > > Actually, I don't think this is what the OP wanted.
Definitely! I'm sure that Samuel meant attaching .ly files to pdf files (like attachments in email), not quoting the source code in markup. I agree that this would be a very useful feature. My source files change even *after* the score was already "published", and sometimes i have trouble when i want to recompile and get the old version. Putting them under version control would help, but i don't think it would solve all the problems. Attaching sources to pdfs gives a really nice way to store music. I prefer to keep finished pdfs separately - for greater clarity, easy searching, easy sharing (my friends wouldn't know what to do with all these source files) and because i also have finale-made pdfs to mix with Lily-made ones. The downsides are that i may not have the sources when i need them or that the pdf doesn't match the source anymore - both of these would be solved by having appropriate .ly files attached to the score. They don't take much space and don't get in the way - really cool! cheers, Janek _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
