From: Sebastian Tennant <sebyte@smolny.plus.com>
To: guile-user@gnu.org
Subject: Re: Error reporting
Date: Sun, 23 Nov 2008 06:18:59 +0000 [thread overview]
Message-ID: <vdufezho.fsf@vps203.linuxvps.org> (raw)
In-Reply-To: 4928962D.6090501@wilsonjc.us
Quoth Jon Wilson <jsw@wilsonjc.us>:
> If this is added, I'd very much recommend including a way to turn it
> off (or more likely to turn it on), as extra noise in error messages
> generally comes at the price of quick understanding. Most of the
> time, timestamps aren't needed, so, except when they are, they are
> noise.
Of course. I was hoping for an environment variable which would need to
be set, something like GUILE_ERROR_TIMESTAMPS_ON.
Guile is my web application scripting language of choice. As a result,
I have dozens of scripts that can be called at any given moment and any
Guile errors appear in my webserver's error log. If Guile errors
included a timestamp, I'd be able to tell which page, and therefore
which script, caused the error, by conslting the access logs (which
already include timestamp information).
I can of course configure my webserver so that it writes one log per
domain, which will help, but error timestamps would be the ultimate
solution.
Sebastian
next prev parent reply other threads:[~2008-11-23 6:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 6:36 Error reporting Sebastian Tennant
2008-11-22 23:30 ` Jon Wilson
2008-11-23 6:18 ` Sebastian Tennant [this message]
2008-11-23 11:48 ` Neil Jerram
2008-11-23 12:29 ` Ludovic Courtès
2008-11-26 17:16 ` Sebastian Tennant
2008-12-01 22:34 ` Neil Jerram
2008-12-02 5:48 ` Sebastian Tennant
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=vdufezho.fsf@vps203.linuxvps.org \
--to=sebyte@smolny.plus.com \
--cc=guile-user@gnu.org \
/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).