From: "Sudarshan S Chawathe" <chaw@eip10.org>
To: spellcard199 <spellcard199@protonmail.com>
Cc: "kawa@sourceware.org" <kawa@sourceware.org>
Subject: Re: Example of run-process with redirection to pipe?
Date: Sun, 25 Aug 2019 18:46:00 -0000 [thread overview]
Message-ID: <20912.1566758722@localhost> (raw)
In-Reply-To: Your message of "Sat, 24 Aug 2019 11:01:13 -0000." <xSkfRJEzkcBfMSLV8mED4Jun6z6ji1idnmuK0YK4Au4NHaeYI9P5DfWxZItqH3DFQg0bWzGM-BuEufGnwku407L0YG-IN72NNzyXN0XLNQI=@protonmail.com>
Thank you very much for the hint; it indeed works when invoked as you
write.
Regards,
-chaw
> Date: Sat, 24 Aug 2019 11:01:13 +0000
> From: spellcard199 <spellcard199@protonmail.com>
> Subject: Re: Example of run-process with redirection to pipe?
>
> Hello. I am also new to kawa, and I don't know why it behaves the way it do=
> es (seems a java permissions thing to me), but you can get the InputStream =
> using:
>
> (gnu.kawa.functions.RunProcess:getInputStreamFrom p)
>
> I found this using "grep -r Stream" inside the Kawa/kawa/lib directory in t=
> he kawa source code, which I found to be a great learning resource.
>
WARNING: multiple messages have this Message-ID
From: "Sudarshan S Chawathe" <chaw@eip10.org>
To: spellcard199 <spellcard199@protonmail.com>
Cc: "kawa@sourceware.org" <kawa@sourceware.org>
Subject: Re: Example of run-process with redirection to pipe?
Date: Fri, 30 Aug 2019 00:04:00 -0000 [thread overview]
Message-ID: <20912.1566758722@localhost> (raw)
Message-ID: <20190830000400.gPNtu4iZ418sqE6Z7WE7ZMb_CtSmt1HO-99A3ou9POA@z> (raw)
In-Reply-To: Your message of "Sat, 24 Aug 2019 11:01:13 -0000." <xSkfRJEzkcBfMSLV8mED4Jun6z6ji1idnmuK0YK4Au4NHaeYI9P5DfWxZItqH3DFQg0bWzGM-BuEufGnwku407L0YG-IN72NNzyXN0XLNQI=@protonmail.com>
Thank you very much for the hint; it indeed works when invoked as you
write.
Regards,
-chaw
> Date: Sat, 24 Aug 2019 11:01:13 +0000
> From: spellcard199 <spellcard199@protonmail.com>
> Subject: Re: Example of run-process with redirection to pipe?
>
> Hello. I am also new to kawa, and I don't know why it behaves the way it do=
> es (seems a java permissions thing to me), but you can get the InputStream =
> using:
>
> (gnu.kawa.functions.RunProcess:getInputStreamFrom p)
>
> I found this using "grep -r Stream" inside the Kawa/kawa/lib directory in t=
> he kawa source code, which I found to be a great learning resource.
>
next prev parent reply other threads:[~2019-08-25 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 17:53 Sudarshan S Chawathe
2019-08-24 11:01 ` spellcard199
2019-08-25 18:46 ` Sudarshan S Chawathe [this message]
2019-08-30 0:04 ` Sudarshan S Chawathe
2019-09-18 18:49 ` Per Bothner
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=20912.1566758722@localhost \
--to=chaw@eip10.org \
--cc=kawa@sourceware.org \
--cc=spellcard199@protonmail.com \
/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).