From: Matt Wette <matt.wette@gmail.com>
To: guile-devel@gnu.org
Subject: Re: GUILE_QUIET=1 guile → suppress REPL welcome message (fixed message format)
Date: Fri, 3 May 2024 12:38:32 -0700 [thread overview]
Message-ID: <2af1c96f-fbd1-40b1-aa45-b9f974bf5b21@gmail.com> (raw)
In-Reply-To: <140234c9-5a15-4f7c-a64c-5fa1948d9b16@gmail.com>
On 3/11/24 6:50 AM, Matt Wette wrote:
> On 3/10/24 6:01 PM, Dr. Arne Babenhauserheide wrote:
>> Hi,
>>
>> It’s been two months now, did anyone get to review this patch?
>>
>> It’s small and it gives an instant improvement when using Guile in Emacs
>> orgmode babel sourceblocks that get evaluated on export.
>>
>> Best wishes,
>> Arne
>>
> 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 had a patch for this at one time, but can't find it right now.
I found it. Here is a link:
https://github.com/mwette/guile-contrib/blob/main/patch/3.0.9/info-port.patch
If you type `guile -I` you get desired behavior. Thinking of changing
to make the info-port /dev/null by default.
Matt
prev parent reply other threads:[~2024-05-03 19:38 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
2024-05-03 19:38 ` Matt Wette [this message]
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=2af1c96f-fbd1-40b1-aa45-b9f974bf5b21@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-devel@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).