* Documentation/user/macros.itexi: don't color glossary links.

* Documentation/user/invoking.itexi (Error messages): new section

diff --git a/ChangeLog b/ChangeLog
index 46556ebe98baa6eddae71e7bccbdcaefbae9e6f0..1b39e928d3a6171d8af70c797393e06958922d59 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2003-07-29  Han-Wen Nienhuys  <hanwen@cs.uu.nl>
+
+       * Documentation/user/macros.itexi: don't color glossary links.
+
+       * Documentation/user/invoking.itexi (Error messages): new section
+
 2003-07-28  Han-Wen Nienhuys  <hanwen@cs.uu.nl>
 
        * input/regression/font-name.ly: add file.

diff --git a/Documentation/user/invoking.itexi b/Documentation/user/invoking.itexi
index 3845651a763777c4f5d8aa6a178121f5f783ba83..90cfca002a50152abc1bb2c19c05c801792217e4 100644 (file)
--- a/Documentation/user/invoking.itexi
+++ b/Documentation/user/invoking.itexi
@@ -7,6 +7,7 @@ This chapter details the technicalities of running LilyPond.
  
 @menu
 * Invoking the lilypond binary::  
+* Error messages::              
 * Reporting bugs::              
 * Point and click::             
 * Invoking ly2dvi::             Titling LilyPond scores.
@@ -200,7 +201,66 @@ This selects the language for the warning messages.
 @cindex LANG
 @cindex LILYPONDPREFIX
 
+@node Error messages
+@section Error messages
+
+@cindex error messages
+Different error messages can appear while compiling a file:
+
+@table @emph
+@cindex warning
+
+@item Warning
+  Something looks suspect. If you are requesting something out of the
+ordinary then you will understand the message, and can ignore it.
+However, warnings usually indicate that something is wrong with the
+input file.
+
+@item Error
+Something is definitely wrong.  The current processing step (parsing,
+interpreting, or formatting) will be finished, but the next step will
+be skipped.
+
+@cindex error
+@cindex fatal error
+@item Fatal error
+Something is definitely wrong, and LilyPond cannot continue. This
+happens rarely. The most usual cause is misinstalled fonts.
+
+@cindex call trace
+@cindex Scheme error
+@item Scheme error
+Errors that occur while executing Scheme code are caught by the Scheme
+interpreter. When they occur, a call trace of the offending function
+is printed.
+
+@cindex Programming error
+@item Programming error
+There was some internal inconsistency. These error messages are
+intended to help the programmers and debuggers. Usually, they can be
+ignored. Sometimes, they come in such big quantities that they obscure
+other output. In this case, a bug-report should be filed.
 
+@end table
+
+@cindex errors, message format
+If warnings and errors can
+be linked to some part of the input file, then error messages have the
+following form
+
+@example
+  @var{filename}:@var{lineno}:@var{columnno}: @var{message}
+  @var{offending input line}
+@end example 
+
+A line-break is inserted in offending line to indicate the column
+where the error was found. For example, 
+
+@example
+test.ly:2:19: error: not a duration: 5:
+  \notes @{ c'4 e'5 
+                   g' @}
+@end example
 
 
 @node Reporting bugs

diff --git a/Documentation/user/macros.itexi b/Documentation/user/macros.itexi
index cac243e64634456c62c78262e10698970f1109f0..1bab2256ecb6809ed582e5c9492fe175fc517556 100644 (file)
--- a/Documentation/user/macros.itexi
+++ b/Documentation/user/macros.itexi
@@ -17,7 +17,9 @@
 @macro rglos {NAME}
 @ifhtml
 @c ugh: @ref assumes that external refs are split documents too
-@uref{../music-glossary.html#\NAME\,\NAME\}@c
+@html
+<a style="text-decoration: none; color: inherit;" href="../music-glossary.html#\NAME\">\NAME\</a>@c
+@end html
 @end ifhtml
 @ifnothtml
 \NAME\@c

diff --git a/scm/define-grobs.scm b/scm/define-grobs.scm
index a6b85bcd298ebb68eb5b1f5fd2edb8c478ecf6fd..8e6e40576b2a0f49ddcfd2e59e87d01d7c95e71d 100644 (file)
--- a/scm/define-grobs.scm
+++ b/scm/define-grobs.scm
@@ -418,7 +418,8 @@
        (breakable . #t)
        (Y-offset-callbacks . (,Self_alignment_interface::aligned_on_self
                               ,Side_position_interface::aligned_on_support_refpoints))
-       ;; huh? what's this for?
+       ;; This direction is for aligned_on_support_refpoints
+       ;; (?) --hwn
        (direction . 0)
        (space-alist . (
                        (left-edge . (extra-space . 1.0))
@@ -498,7 +499,6 @@
        (font-family . roman)
        (font-shape . upright)
        
-       ;; duh, side-position-interface?
        (meta . ((interfaces . (rhythmic-grob-interface lyric-syllable-interface self-alignment-interface text-interface font-interface item-interface ))))
        ))