---

Bug reporting

If you have input that results in a crash or an erroneous output, then that is a bug. There is a list of current bugs on our google bug tracker,

http://code.google.com/p/lilypond/issues/list

If you have discovered a bug which is not listed, please help us by sending an input file which demonstrates the problem to the bug-lilypond list. Unfortunately there is a strict “no top-posting” check on gmane; to avoid this, add

> I'm not top posting.

(you must include the > ) to the top of your bug report.

Please DO NOT add bug reports directly to the bug tracker. Once an issue has been added to the tracker, feel free to add more information to that report.

When creating a file, please

• Include the \version number.
• Create an example which is as small as possible. Most bugs can be duplicated in less than ten lines of LilyPond code. Unfortunately we do not have the resources to debug large examples.
• Almost every bug can be reproduced with four notes or less. Bugs about spacing or page layout might require many bars of music, but other bugs can probably be reproduced using only a single measure.
• Avoid using complicated notes, keys, or time signatures, unless the bug is about the behavior of those items.
• Do not use \override commands unless the bug is about those particular commands.
• If possible, use \paper{ ragged-right=##t } at the top of your example.

Here's an example of a good bug report:

%% the octavation command doesn't do anything.

\version "2.10.0"
\paper{ ragged-right=##t }
\relative c''' {
  c1
  #(set-octavation 1)
  c1
}

Once your bug has been accepted to the bug tracker, you may mark the bug so that you automatically receive emails when any activity on the bug occurs. This requires you have a google account. Even better, if you are suscribed to bug-lilypond, you will receive emails for all activity on the bug tracker.

---