Suggestions for writing LilyPond files - GNU LilyPond
Description: GNU LilyPond

Next: Saving typing with identifiers and functions, Up: Working on LilyPond projects

### 4.1 Suggestions for writing LilyPond files

Now you're ready to begin writing larger LilyPond files – not just the little examples in the tutorial, but whole pieces. But how should you go about doing it?

As long as LilyPond can understand your files and produces the output that you want, it doesn't matter what your files look like. However, there are a few other things to consider when writing lilypond files.

- What if you make a mistake? The structure of a lilypond file can make certain errors easier (or harder) to find.
- What if you want to share your files with somebody else? In fact, what if you want to alter your own files in a few years? Some lilypond files are understandable at first glance; other files may leave you scratching your head for an hour.
- What if you want to upgrade your lilypond file for use with a later version of lilypond? The input syntax changes occasionally as lilypond improves. Most changes can be done automatically with `convert-ly`, but some changes might require manual assistance. Lilypond files can be structured in order to be easier (or header) to update.

Next: Saving typing with identifiers and functions, Up: Working on LilyPond projects

This page is for LilyPond-2.10.33 (stable-branch).

Other languages: French.