parse scm fixes

diff --git a/ChangeLog b/ChangeLog
index bfa215065af48b2e8fbf8e869a365ae9eea73721..c306d2c931cdeb19e6097d1030f4da24c0529ede 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2002-07-30  Han-Wen  <hanwen@cs.uu.nl>
+
+       * lily/parse-scm.cc (parse_handler): add better error message,
+       return a sensible number of nchars
+
 2002-07-29  Han-Wen Nienhuys  <hanwen@cs.uu.nl>
 
        * lily/parse-scm.cc (protected_ly_parse_scm): catch GUILE errors

diff --git a/lily/parse-scm.cc b/lily/parse-scm.cc
index e5228d945ccad67ac250c6cfb9d28fd66b4641cd..66f46482e5f492741d5dc736316440de42c64ad6 100644 (file)
--- a/lily/parse-scm.cc
+++ b/lily/parse-scm.cc
@@ -79,8 +79,15 @@ parse_handler (void * data, SCM tag, SCM args)
 
   ps->start_location.error (_("GUILE signaled an error for the expression begining here"));
 
-  gh_display (args);
-  gh_newline();
+  if (scm_ilength (args) > 2)
+    scm_display_error_message (gh_cadr (args), gh_caddr(args), scm_current_error_port());
+
+  /*
+    The following is a kludge; we should probably search for
+    [a-z][0-9] a note, and start before that.
+   */
+  ps->nchars = 1;
+    
   return SCM_EOL;
 }