From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: GUILE_QUIET=1 guile → suppress REPL welcome message (fixed message format)
Date: Mon, 11 Mar 2024 20:41:13 +0100 [thread overview]
Message-ID: <871q8gr1cw.fsf@web.de> (raw)
In-Reply-To: <140234c9-5a15-4f7c-a64c-5fa1948d9b16@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
Hi Matt,
Matt Wette <matt.wette@gmail.com> writes:
> On 3/10/24 6:01 PM, Dr. Arne Babenhauserheide wrote:
> It’s small and it gives an instant improvement when using Guile in Emacs
> orgmode babel sourceblocks that get evaluated on export.
>
> I did look at it. Another solution, I prefer, is generate a global urrent-info-port object and
> provide a command-line option to make that a file or /dev/null. Send the welcome and
> auto-compile messages to (current-info-port).
I don’t mind the internal implementation. So I chose the option with the
lowest impact on other parts of Guile.
However I chose to use an environment variable because it makes it
easier to adjust the behavior for special situations without bloating
the interface used by most people.
> I had a patch for this at one time, but can't find it right now.
I’ll gladly review it if you find it again. For such small changes I can
also push.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2024-03-11 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 13:43 GUILE_QUIET=1 guile => suppress REPL welcome message Dr. Arne Babenhauserheide
2024-01-09 15:50 ` GUILE_QUIET=1 guile → suppress REPL welcome message (fixed message format) Dr. Arne Babenhauserheide
2024-03-11 1:01 ` Dr. Arne Babenhauserheide
2024-03-11 13:50 ` Matt Wette
2024-03-11 19:41 ` Dr. Arne Babenhauserheide [this message]
2024-05-03 19:38 ` Matt Wette
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=871q8gr1cw.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-devel@gnu.org \
--cc=matt.wette@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).