From: Jean Louis <guix@rcdrun.com>
To: 23349@debbugs.gnu.org
Subject: bug#23349: Compile output shall be error output
Date: Sat, 23 Apr 2016 13:36:30 +0200 [thread overview]
Message-ID: <20160423113630.GA22901@protected.rcdrun.com> (raw)
When editing a guile file and running it, it is going to compile it, and
there are warnings:
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-auto-compile argument to disable.
;;; compiling /home/data1/protected/bin/webm2html
;;; compiled
;;; /home/data1/protected/.cache/guile/ccache/2.0-LE-8-2.0/home/data1/protected/bin/webm2html.g\
o
This kind of warnings is not desired in the output of the command and
warning shall be given on the error output and not on standard output,
so that it is possible, just with any other programs to redirect the
warnings to dev null, for example: myguile.scm 2 > /dev/null, to avoid
such warnings.
This does not work as warnings are given on standard output.
Jean Louis
next reply other threads:[~2016-04-23 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 11:36 Jean Louis [this message]
2016-06-25 20:12 ` bug#23349: Compile output shall be error output Matt Wette
2016-06-25 20:54 ` Matt Wette
2017-02-28 15:07 ` Andy Wingo
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=20160423113630.GA22901@protected.rcdrun.com \
--to=guix@rcdrun.com \
--cc=23349@debbugs.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).