From: Graham Percival <graham@percival-music.ca>
Date: Mon, 13 Sep 2004 02:06:30 +0000 (+0000)
Subject: Updated "reporting bugs".
X-Git-Tag: release/2.3.17~44
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=5c0a7e68b60e355d61c4b1b6c556581eba17cd24;p=lilypond.git

Updated "reporting bugs".
---

diff --git a/ChangeLog b/ChangeLog
index e5ba0c450f..6bf4432a14 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -2,6 +2,8 @@
 
 	* Documentation/user/notation.itely: fixed Time Signature numbers bug.
 
+	* Documentation/user/invoking.itexi: updated the "reporting bugs" section.
+
 2004-09-12  Han-Wen Nienhuys   <hanwen@xs4all.nl>
 
 	* scm/define-grobs.scm (all-grob-descriptions): longer
diff --git a/Documentation/user/invoking.itexi b/Documentation/user/invoking.itexi
index ff9d27de19..92ed451dd4 100644
--- a/Documentation/user/invoking.itexi
+++ b/Documentation/user/invoking.itexi
@@ -280,39 +280,37 @@ If you have input that results in a crash or an erroneous output, then
 that is a bug.  We try respond to bug-reports promptly, and fix them as
 soon as possible.  Help us by sending a defective input file, so we can
 reproduce the problem.  Make it small, so we can easily debug the
-problem.  Don't forget to tell which version you use, and on which
-platform you run it.  Send the report to
-@email{bug-lilypond@@gnu.org}.
+problem.  Don't forget to tell which version of LilyPond you use!  Send
+the report to @email{bug-lilypond@@gnu.org}.
 
-FIXME: devel bug reports go to...?
+When you've found a bug, have a look at our
+@uref{http://lilypond.org/doc/v2.3/bugs/,bug database} to see if it
+has already been reported.  You could also try doing a few searches
+on the mailing list for the bug.  Sometimes the bug will have already
+been reported and a fix or workaround is already known.
 
-@c yeah, normally these go in comments, but they'll be fixed -very- soon,
-@c  and I wanted to make it clear to people reading the devel docs that
-@c  these facts need clarification.  -gp
-FIXME: does bug-lilypond get archived?
+Here's an example of a good bug report:
 
-@c  TODO: make a link to the archive/search for html output
-When you've found a bug, do a few searches on the mailing list for
-the bug.  Sometimes the bug will have already been reported and a fix
-or workaround is already known.
+@verbatim
 
-@c  I'm not going to mention the bug CVS.  Newbies won't know how to
-@c  use it, and it would only scare them.  Besides, Erik says he doesn't
-@c  mind getting multiple bug reports, so who cares if it makes more work
-@c  for him?  :)     (in addition, multiple bug reports about the same
-@c  thing could be useful in judging the severity of a problem)   -gp
+It seems that placement of accidentals is broken. In the
+following example, the accidental touches the note head.
 
-Here's an example of a good bug report:
+Using Mac OSX 10.3.5, fink package lilypond-unstable
 
-@example
-% LilyPond 2.3.11, Mac OSX 10.3.4, fink package lilypond-unstable
-% slur does not look at accidentals
-\score @{
-\relative c''@{
-a1 a a a a
-a2. g16( b d fis)
-@}@}
-@end example
+\version "2.3.16"
+\relative c''{
+   a4 b cis d
+}
+@end verbatim
+
+@lilypond
+\version "2.3.16"
+\relative c''{
+   \override Accidental #'extra-offset = #'(1.0 . 0) 
+   a4 b cis d
+}
+@end lilypond
 
 @node Editor support
 @section Editor support