[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How can I tell guile to shut up? ;)
From: |
Andy Wingo |
Subject: |
Re: How can I tell guile to shut up? ;) |
Date: |
Tue, 28 Jun 2011 23:52:38 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) |
Hi,
On Thu 31 Mar 2011 13:11, Andy Wingo <address@hidden> writes:
> On Wed 02 Mar 2011 09:22, "Juhani Viheräkoski" <address@hidden> writes:
>
>> $ ./test-script
>> ;;; note: source file /home/misty/moonshine/yarg/scripts/./race
>> ;;; newer than compiled
>> /home/misty/.cache/guile/ccache/2.0-LE-4-2.0/home/misty/moonshine/yarg/scripts/test-script.go
>> ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
>> ;;; or pass the --no-auto-compile argument to disable.
>> ;;; compiling /home/misty/moonshine/yarg/scripts/./test-script
>> ;;; compiled
>> /home/misty/.cache/guile/ccache/2.0-LE-4-2.0/home/misty/moonshine/yarg/scripts/test-script.go
>
>> It seems there is no option to disable these annoying messages in guile
>> 2.0. I do scripts using guile and I would appreciate not getting these
>> messages that interfere with other output. It is possible to use
>> 2>/dev/null but what would I do if my script would output error messages
>> (as it will probably do at some point)?
>
> I entirely agree that it's a problem. By default, running a Guile
> script should not cause Guile itself to print anything, to any port.
>
> These messages are useful at times, but they were more useful last year
> when compilation didn't work as well as it does now, and they could
> probably be pared down a bit.
[...]
>
>> My suggestion is to add option --quiet to guile.
>
> Hmm. I think prefer adding -Wfoo, for warnings, like GCC does. It's
> not getopt-long compatible, but we already have -ds. For other
> informational messages, it does seem that we need something like
> --quiet, or --verbosity=..., or something. Not quite sure what that
> is. I've copied guile-devel on this mail to see if anyone else has
> opinions on this.
After some thinking, the base thing to do is just to add a warning port,
and make warnings (non-fatal informative messages) write to that port.
I have done this in the attached patches. Any objections?
Andy
0001-add-current-warning-port.patch
Description: Text Data
0002-warnings-written-to-warning-port.patch
Description: Text Data
--
http://wingolog.org/
- Re: How can I tell guile to shut up? ;),
Andy Wingo <=