From: Peter TB Brett <peter@peter-b.co.uk>
To: guile-user@gnu.org
Subject: Quietening Guile compilation output
Date: Fri, 27 Sep 2013 21:56:39 +0100 [thread overview]
Message-ID: <8738oq2dbs.fsf@harrington.peter-b.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
Hi folks,
As my Scheme codebase gets larger, when starting my application I get
screens full of debug spew about the Guile compilation process. How can
I silence the following messages:
;;; note: source file /path/to/foo.scm
;;; newer than compiled /path/to/foo.scm.go
;;; compiling /path/to/foo.scm
;;; compiled /path/to/foo.scm.go
...while still getting the actually useful compilation warnings?
Thanks,
Peter
P.S. Bonus points if you can help me find an approach that can be used
without causing errors when the code is run under Guile 1.8...!
--
Dr Peter Brett <peter@peter-b.co.uk>
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2013-09-27 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 20:56 Peter TB Brett [this message]
2013-09-28 9:40 ` Quietening Guile compilation output Thien-Thi Nguyen
2013-09-28 9:48 ` Peter TB Brett
2013-09-28 12:51 ` Ludovic Courtès
2013-09-28 16:13 ` Peter TB Brett
2013-09-28 22:12 ` Ludovic Courtès
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=8738oq2dbs.fsf@harrington.peter-b.co.uk \
--to=peter@peter-b.co.uk \
--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).