mirror/guile
mirror/guile
1
Fork 0
mirror of https://git.savannah.gnu.org/git/guile.git synced 2025-06-12 14:50:19 +02:00
Code Activity

(Debug Last Error): Line break in "Type

Browse source 
(backtrace) to get ..." which overflowed the line in both info and
DVI.  Reported by Percy Tiglao.
This commit is contained in:
Kevin Ryde 2006-09-07 20:49:12 +00:00
parent dc1cac02eb
commit ceafa69a71
1 changed files with 10 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

12
doc/ref/scheme-debugging.texi
View file

@ -1,6 +1,6 @@
@c -*-texinfo-*- @c -*-texinfo-*-
@c This is part of the GNU Guile Reference Manual. @c This is part of the GNU Guile Reference Manual.
@c Copyright (C) 1996, 1997, 2000, 2001, 2002, 2003, 2004 @c Copyright (C) 1996, 1997, 2000, 2001, 2002, 2003, 2004, 2006
@c Free Software Foundation, Inc. @c Free Software Foundation, Inc.
@c See the file guile.texi for copying conditions. @c See the file guile.texi for copying conditions.
@ -43,6 +43,8 @@ the error occurred. By default, Guile then displays only the most
immediate information about where and why the error occurred, for immediate information about where and why the error occurred, for
example: example:
@c Note: line break in "enter the debugger" to avoid an over-long
@c line in both info and DVI.
@lisp @lisp
(make-string (* 4 (+ 3 #\s)) #\space) (make-string (* 4 (+ 3 #\s)) #\space)
@print{} @print{}
@ -50,7 +52,8 @@ standard input:2:19: In procedure + in expression (+ 3 #\s):
standard input:2:19: Wrong type argument: #\s standard input:2:19: Wrong type argument: #\s
ABORT: (wrong-type-arg) ABORT: (wrong-type-arg)
Type "(backtrace)" to get more information or "(debug)" to enter the debugger. Type "(backtrace)" to get more information or "(debug)" to enter
the debugger.
@end lisp @end lisp
@noindent @noindent
@ -1043,3 +1046,8 @@ behaviour as well as the more traditional @code{trace-here}.
The older mechanism will probably become obsolete eventually, but it's The older mechanism will probably become obsolete eventually, but it's
worth keeping it around for a while until we are sure that the new worth keeping it around for a while until we are sure that the new
mechanism is correct and does what programmers need. mechanism is correct and does what programmers need.
@c Local Variables:
@c TeX-master: "guile.texi"
@c End: