From: <tomas@tuxteam.de>
To: guile-devel@gnu.org
Subject: Re: help needed with stderr redirection
Date: Sat, 22 Oct 2022 08:26:05 +0200 [thread overview]
Message-ID: <Y1OM/Y4bV+BqEIaE@tuxteam.de> (raw)
In-Reply-To: <875ygceop6.fsf@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
On Sat, Oct 22, 2022 at 01:29:05AM +0200, Csepp wrote:
> I have this short snippet of code for a Guix related utility script and
> for the love of the Glowcloud it does not want to work. I want to
> filter stderr for certain lines and they are not being redirected. When
> running the full script from a shell, it correctly captures standard
> out, but all the warnings and errors from the subprocess and/or its
> children go directly to the terminal.
>
> I looked in the Guix sources to see how others do it and found mention
> of a possibly related bug:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52835
> Is that still relevant? Because debuggs is just, khm, great, I don't
> see any clear indication of what its status is.
>
> (define (with-input-from-make thunk)
> (with-error-to-port
> (current-output-port)
> (lambda _
> (with-input-from-port
> (open-pipe* OPEN_READ "make")
> thunk))))
I think `with-error-to-port' just directs the error messages of the
current process. Not the ones of the subprocess you are invoking with
open-pipe*. Could that be the case?
To get a better idea of what's going on, you can let a subshell handle
that redirection for you, substitute `open-pipe*' with the star-less
variable and try:
(open-pipe OPEN_READ "make 2>&1")
If that works as you expect, you can work your way from there. If not,
we've learnt something :)
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-10-22 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 23:29 help needed with stderr redirection Csepp
2022-10-22 6:26 ` tomas [this message]
2022-10-22 8:23 ` Josselin Poiret
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=Y1OM/Y4bV+BqEIaE@tuxteam.de \
--to=tomas@tuxteam.de \
--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).