From: Wolfgang Jaehrling <pro-linux@gmx.de>
Subject: Improving error messages
Date: Sun, 2 Mar 2003 14:01:05 +0100 [thread overview]
Message-ID: <20030302130105.GC422@gmx.de> (raw)
Hi!
I think that a weak point of Guile are the error messages, which are
often very terse. This is not much of a problem once you are used to
it and know what the messages refer to, but when I was new to Guile
(and new to Scheme at the same time), this was a major problem for me.
Thus, I decided to try my best to make Guile more newbie-friendly. At
<http://www.8ung.at/shell/guile.patch> you find a very incomplete
patch, and I would like to know if it goes into the right direction at
all: Is this the kind of stuff you would want?
Cheers,
GNU/Wolfgang
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2003-03-02 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 13:01 Wolfgang Jaehrling [this message]
2003-03-04 21:31 ` Improving error messages Rob Browning
2003-03-19 19:48 ` Marius Vollmer
2003-03-23 13:04 ` Wolfgang Jaehrling
2003-03-23 20:33 ` Marius Vollmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030302130105.GC422@gmx.de \
--to=pro-linux@gmx.de \
--cc=wolfgang@pro-linux.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).