From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: guile-user@gnu.org
Subject: Re: Shell commands with output to string
Date: Tue, 22 Feb 2022 09:38:35 +0000 [thread overview]
Message-ID: <1280eba0-81c0-6e7b-d512-bbd1f83a409c@posteo.de> (raw)
In-Reply-To: <e6859100-a234-37b9-c677-3e72f36f0578@posteo.de>
Corrections below.
On 2/22/22 10:29, Zelphir Kaltstahl wrote:
> Hello Guile users!
>
> How would I run a shell command from inside Guile and get its output as a
> string, instead of the output being outputted directly? (Guile 3.0.8)
>
> So far I have found
>
> ~~~~
> (system ...)
> ~~~~
>
> which I tried to use with
>
> ~~~~
> scheme@(guile-user)> (with-output-to-string
> (system "ls -al"))
>
> ;; lots of output immediately shown and not stored in variable
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> Wrong type to apply: 0
>
> Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
> scheme@(guile-user) [1]> ,bt
> In ice-9/ports.scm:
> 476:4 2 (with-output-to-string 0)
> While executing meta-command:
> In procedure frame-local-ref: Argument 2 out of range: 1
> ~~~~
>
> But this does not give me a string back.
>
> I also tried with
>
> ~~~~
> scheme@(guile-user)> (call-with-values (lambda () (system "ls -al"))
> ... (lambda (exit-code output) output))
>
> ;; lots of output immediately shown
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> Wrong number of values returned to continuation (expected 2)
>
> Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
>
> scheme@(guile-user) [1]> ,bt
> In current input:
> 10:29 1 (_)
> In ice-9/boot-9.scm:
> 1685:16 0 (raise-exception _ #:continuable? _)
> ~~~~
>
> Is there another function I should be using?
>
> I would like to have the exit code and the output of a command.
>
> Best regards,
> Zelphir
Of course I should use `with-output-to-string` correctly:
~~~~
scheme@(guile-user)> (with-output-to-string
(lambda () (system "ls -al")))
;; directly outputted stuff
$1 = ""
~~~~
But still not a win.
Regards,
Zelphir
--
repositories: https://notabug.org/ZelphirKaltstahl
next prev parent reply other threads:[~2022-02-22 9:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 9:29 Shell commands with output to string Zelphir Kaltstahl
2022-02-22 9:38 ` Zelphir Kaltstahl [this message]
2022-02-22 10:20 ` Alex Sassmannshausen
2022-02-22 10:43 ` post
2022-02-23 14:01 ` Josselin Poiret
2022-03-08 23:12 ` Zelphir Kaltstahl
2022-03-09 14:14 ` Josselin Poiret
2022-02-22 11:20 ` Neil Jerram
2022-02-23 1:28 ` Zelphir Kaltstahl
2022-02-23 1:29 ` Zelphir Kaltstahl
2022-02-22 10:21 ` tomas
2022-02-22 14:27 ` Olivier Dion via General Guile related discussions
2022-02-22 16:00 ` Leo Butler
2022-02-22 16:33 ` Olivier Dion via General Guile related discussions
2022-02-23 1:26 ` Zelphir Kaltstahl
2022-02-23 14:13 ` Olivier Dion via General Guile related discussions
2022-02-26 0:32 ` Zelphir Kaltstahl
-- strict thread matches above, loose matches on Subject: below --
2022-02-23 17:48 Blake Shaw
2022-02-23 18:25 ` Olivier Dion via General Guile related discussions
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=1280eba0-81c0-6e7b-d512-bbd1f83a409c@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guile-user@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).