From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: 40367@debbugs.gnu.org
Subject: [bug#40367] [PATCH] lint: Display result of checkers on stdout.
Date: Wed, 01 Apr 2020 14:25:52 +0200 [thread overview]
Message-ID: <877dyzjstr.fsf@nckx> (raw)
In-Reply-To: <20200401073835.5890-1-brice@waegenei.re>
[-- Attachment #1: Type: text/plain, Size: 678 bytes --]
Brice,
Thanks! As discussed on IRC, I agree stdout is better. These are
reports, not run-time errors.
Brice Waegeneire 写道:
> * guix/scripts/lint.scm (run-checkers): Replace
> 'current-error-port' by
> 'current-output-port'.
It should still print *progress* messages (and any run-time
warnings & errors) to stderr, though:
$ guix lint sl >toot
checking sl@5.02[cve]...
$ guix lint sl >toot
guix lint: error: something bad happened
This includes reverting to (isatty? (current-error-port));
stdout's ttyness doesn't matter.
Please also rebase your revisions onto current master
(particularly 57e12aa).
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-04-01 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 7:38 [bug#40367] [PATCH] lint: Display result of checkers on stdout Brice Waegeneire
2020-04-01 12:25 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-04-01 13:21 ` Brice Waegeneire
2020-04-21 8:58 ` Brice Waegeneire
2020-04-01 13:19 ` [bug#40367] [PATCH v2] " Brice Waegeneire
2020-05-21 19:08 ` [bug#40367] [PATCH v3] " Brice Waegeneire
2020-11-21 10:24 ` bug#40367: " Christopher Baines
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dyzjstr.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=40367@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.