Next: , Previous: Output, Up: Usage


3.3 Initialization File

When FOMUS starts up, it searches for an initialization file named .fomus in your home directory. You must create yourself if it doesn't already exist. Use this file to modify FOMUS's default behavior by changing setting values. The syntax is flexible, and can be one of ‘setting = value’, ‘setting: value’ and ‘setting value’. Examples of some useful initialization file settings are:

     // Set the documentation use level to 0, the level for total newbies.
     use-level = 0
     
     // Set verbosity to 2, the highest value (0 is the lowest).
     verbose = 2
     
     // Set the path to the LilyPond executable, so FOMUS automatically processes
     // LilyPond output files.
     lily-exe-path = "/usr/bin/lilypond"
     
     // Set the path to a .pdf viewer application, so FOMUS automatically displays
     // the results.
     lily-view-exe-path = "evince"
     // A Windows example:
     lily-exe-path = "C:\\Program Files\\Adobe\\Reader 9.0\\Reader\\AcroRd32.exe"
     
     // If you don't specify an output filename anywhere, this will be the default.
     filename = "/tmp/out.ly"
     
     // Always produce a .fms, .xml and .ly file.
     output = (fms xml ly)

This is also a good place for adding extensions to FOMUS's instrument and percussion instrument libraries (see `.fms' File Examples for examples of defining instruments and percussion instruments).

     inst-defs += (<id my-special-inst ...> <id another-special-inst ...> ...)
     
     percinst-defs += (<id my-special-percinst ...> <id another-special-percinst ...> ...)
     
     layout-defs += (my-ensemble (kazoo ukulele glockenspiel organ))