From: Panisuan Chasinga <jo.chasinga@gmail.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: How to read a string output with `open-input-pipe` on Mac OS?
Date: Tue, 10 Oct 2023 16:07:57 -0700 [thread overview]
Message-ID: <CADvidhEcJyJFrwSw_HivV=crrhe1QY5FF_V6jDD2=QhEGi6R6g@mail.gmail.com> (raw)
In-Reply-To: <ec550f17-326a-4736-bfa1-95d293d3845b@posteo.de>
Thanks for sharing the code. However, after running the function on any
command like `ls` or `date`, the function only returns two #<eof>. I got an
#<eof> too with this code:
(define (test-read)
(let* ((p (open-input-pipe "ls"))
(str (read-delimited "" p)))
(close-port p)
str))
(test-read)
I'm now almost positive this might be a Mac OS-related bug.
On Tue, Oct 10, 2023 at 3:41 AM Zelphir Kaltstahl <
zelphirkaltstahl@posteo.de> wrote:
> On 10/10/23 02:49, Panisuan Chasinga wrote:
> > Hi list, I want to read a string output using
> `ice-9/popen/open-input-pipe`
> > but somehow always got an empty string. Here is my test code:
> >
> >
> > (use-modules (ice-9 popen))
> > (use-modules (ice-9 textual-ports))
> >
> > (define (test-read-port)
> > (let* ((port (open-input-pipe "ls"))
> > (str (get-string-all p)))
> > (close-port p)
> > str))
> >
> >
> > I was able to read from a file with `open-input-file`, but not
> > `open-input-pipe` with any command. Running `(system "ls")` seemed to
> work
> > just fine.
>
> Hello Panisuan,
>
> perhaps this code can help you as well:
>
> https://notabug.org/ZelphirKaltstahl/guile-examples/src/22bf7be3ae46a7b520c1482ab80985bfbdae6eb6/input-output/stdout-stderr.scm
>
> It handles also error output.
>
> Best regards,
> Zelphir
>
> --
> repositories: https://notabug.org/ZelphirKaltstahl
>
>
next prev parent reply other threads:[~2023-10-10 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 0:49 How to read a string output with `open-input-pipe` on Mac OS? Panisuan Chasinga
2023-10-10 4:31 ` tomas
2023-10-10 10:41 ` Zelphir Kaltstahl
2023-10-10 23:07 ` Panisuan Chasinga [this message]
[not found] <FA53E38F-EED0-463E-9A51-BF07AAB5718C@fil.org>
2023-10-11 4:21 ` tomas
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='CADvidhEcJyJFrwSw_HivV=crrhe1QY5FF_V6jDD2=QhEGi6R6g@mail.gmail.com' \
--to=jo.chasinga@gmail.com \
--cc=guile-user@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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).