I don't know if that's a too complex solution, but you could try the following:
- write the individual parts of your source in individual files
- write two alternative intermediate files:
  - one that \includes all the parts (like "production.ily")
- one that \includes only the parts you want to be used (like "notYet.ily") - in your final lilypond file \include these two files but comment out one of them.

HTH
Urs

Am 18.02.2012 00:30, schrieb Michael Hendry:
When I've finished a jazz chart, I'll want to produce separate parts for several transposing instruments, but while I'm working on the entry of the melody and chords in concert pitch I only need to produce one .pdf file. Obviously, I can comment out the sections I don't want during data entry work, and remove the comments once the work is complete, but it would be handy to be able to use a C-like construct like this: *#DEFINE NotYet ... #IFNDEF NotYet \book { \bookOutputName "Chez Fernand (alto)" \new Score << \transpose f' d {\TheChords} \new Staff \repeat unfold 13 { s1 \noBreak s1 \noBreak s1 \noBreak s1 \break } \transpose f' d {\TheHead} >> \header {piece = "Alto Sax"} } #ENDIF * to suppress unwanted output for the Alto sax part (and those for the other transposing instruments), and comment out the #DEFINE NotYet when I'm happy with the data entry.
------------------------------------------------------------------------
View this message in context: Is there an equivalent of #define ... #ifndef ... #endif in lilypond? <http://old.nabble.com/Is-there-an-equivalent-of--define-...--ifndef-...--endif-in-lilypond--tp33346188p33346188.html> Sent from the Gnu - Lilypond - User mailing list archive <http://old.nabble.com/Gnu---Lilypond---User-f1722.html> at Nabble.com.


_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to