From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: John Cowan <cowan@ccil.org>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Logging in Guile
Date: Wed, 15 Jan 2020 00:51:07 +0100 [thread overview]
Message-ID: <3151e2cb-f6be-f3e9-23e4-6646fab64bab@posteo.de> (raw)
In-Reply-To: <CAD2gp_StisKU1q58grcVWG1bpu61=V3BRYPKxV_anekmtuC53Q@mail.gmail.com>
Thanks, I will also take a look at that!
On 1/13/20 7:47 PM, John Cowan wrote:
> I have a rough proposal now at
> <https://bitbucket.org/cowan/r7rs-wg1-infra/src/default/SyslogCowan.md>.
> It depends on either being able to send TCP or UDP packets or
> preferably to call the Posix API through the FFI. It is very basic
> and leaves log rotation etc. to the syslog infrastructure.
>
> On Mon, Jan 13, 2020 at 1:10 PM Zelphir Kaltstahl
> <zelphirkaltstahl@posteo.de <mailto:zelphirkaltstahl@posteo.de>> wrote:
>
> Hi Guile Users!
>
> Is there any library for logging in Guile?
>
> What I imagine is something, where I can log messages of various
> levels,
> like debug, info, error and such. Currently I am using display and
> simple-format for all the things, but it would be nice to be able
> to run
> a program and give it some log level, so that only the log messages of
> that level or above in importance are shown. Then I could leave all my
> logging in my code and set it to debug level or, if intended to be
> seen
> for the user, set it to info level, or if there really is an error, I
> could set it to error level.
>
> On a quick search I could not find anything.
>
> Regards,
> Zelphir
>
>
next prev parent reply other threads:[~2020-01-14 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 18:06 Logging in Guile Zelphir Kaltstahl
2020-01-13 18:17 ` Alex Sassmannshausen
2020-01-14 23:07 ` Zelphir Kaltstahl
2020-01-13 18:47 ` John Cowan
2020-01-14 23:51 ` Zelphir Kaltstahl [this message]
2020-01-13 21:42 ` Roel Janssen
2020-01-14 23:53 ` Zelphir Kaltstahl
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=3151e2cb-f6be-f3e9-23e4-6646fab64bab@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=cowan@ccil.org \
--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).