unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Jean Abou Samra <jean@abou-samra.fr>,
	Nala Ginrut <nalaginrut@gmail.com>,
	Matias Jose Seco Baccanelli <matias_jose_seco@autoproduzioni.net>,
	guile-user@gnu.org
Subject: Re: Curiosity: Microkernel implemented in Guile ?
Date: Sun, 26 Jun 2022 09:55:09 +0200	[thread overview]
Message-ID: <87y1xjamdz.fsf@elephly.net> (raw)
In-Reply-To: <87fsjrap6t.fsf@web.de>


"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:

> - The compilation-messages (I hate them; these also hurt when writing
>   interactive utilities for the command-line, and I have too many
>   half-working fixes in script files to still be comfortable; I think I
>   once had a fix in configuration, but I lost it again — or maybe I had
>   just hacked Guile)

I use compilation (of Wisp) in the GWL and I silence output while
compiling by redirecting the current-error-port / current-output-port.

-- 
Ricardo



  reply	other threads:[~2022-06-26  7:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  6:11 Curiosity: Microkernel implemented in Guile ? Matias Jose Seco Baccanelli
2022-06-23  6:57 ` Mikael Djurfeldt
2022-06-23  9:01   ` Ricardo G. Herdt
2022-06-24  5:40     ` Dr. Arne Babenhauserheide
2022-06-23  7:02 ` Dr. Arne Babenhauserheide
2022-06-23  7:32 ` zimoun
2022-06-23  7:34 ` Maxime Devos
2022-07-02  9:47   ` Matias Jose Seco Baccanelli
2022-07-04  2:49     ` Blake Shaw
2022-06-23  9:13 ` pukkamustard
2022-06-23 10:09 ` Nala Ginrut
2022-06-23 11:22   ` Maxime Devos
2022-06-23 15:38   ` Nala Ginrut
2022-06-23 22:03     ` Dr. Arne Babenhauserheide
2022-06-24  1:12       ` Nala Ginrut
2022-06-24  5:45         ` Dr. Arne Babenhauserheide
2022-06-24  7:01         ` Jean Abou Samra
2022-06-24  7:41           ` Dr. Arne Babenhauserheide
2022-06-25 14:35             ` Jean Abou Samra
2022-06-26  6:22               ` Dr. Arne Babenhauserheide
2022-06-26  7:55                 ` Ricardo Wurmus [this message]
2022-06-26  8:32                   ` Dr. Arne Babenhauserheide
2022-06-28 22:23                 ` Jean Abou Samra
2022-06-26 10:37               ` Nala Ginrut
2022-06-28 22:30                 ` Jean Abou Samra
2022-06-24 12:42           ` Nala Ginrut
2022-06-24  3:27       ` Ognen Duzlevski
2022-06-24 21:24         ` Dr. Arne Babenhauserheide
2022-06-23 12:13 ` Ognen Duzlevski
2022-06-23 13:30   ` Dr. Arne Babenhauserheide
2022-06-23 17:47     ` Paul Emsley

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=87y1xjamdz.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=arne_bab@web.de \
    --cc=guile-user@gnu.org \
    --cc=jean@abou-samra.fr \
    --cc=matias_jose_seco@autoproduzioni.net \
    --cc=nalaginrut@gmail.com \
    /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).