From: Orm Finnendahl <o.finnendahl@mh-freiburg.de>
To: "Sven Schäfer" <sven-schaefer-ww@web.de>
Cc: guile-user@gnu.org
Subject: Re: console info
Date: Sat, 8 May 2010 12:03:49 +0200 [thread overview]
Message-ID: <20100508100349.GB28863@varese> (raw)
In-Reply-To: <2A612F7112B54D1DA52B54DA21692B1A@SvenPC>
Hi Sven,
I don't know whether there is a way to change the prompt to disappear
completely without changing the sources (as this is generally not the
intended behaviour) but as a workaround you could pipe the guile
output through sed to remove the prompt. Try this command in a
terminal:
guile | sed -e 's/^guile>//g'
That should do what you want. You can do that programmatically as well
or invoke this as a script from within your program.
In general your approach seems strange to me. Without exactly knowing
how to do it I'd suggest you look for a way to approach guile's read
routine directly and handle the results internally rather than dealing
with netcat and stdout.
--
Orm
Am Saturday, den 08. May 2010 um 08:28:38 Uhr (+0200) schrieb Sven Schäfer:
>
>
> Hi obj.
>
>
>
> I forgot to write that I will use Guile on a linux system.
>
> Only the output “guile>” should be disable. All other outputs from Guile
> should go to the stdout.
>
>
>
> A short overview:
>
> I will write the output from Guile in variables. A second program
> communicates with the “Guile”-program over netcat. This program sends
> instructions to the Guile program. Then the Guile program returns some
> data (for example an integer). When I now write the output in the second
> program into a variable, I write also the “guile>” into it. Because of
> this I will only disable the output of “guile>”.
>
>
>
> I hope I write this a little bit understandable. J
next prev parent reply other threads:[~2010-05-08 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 19:28 (no subject) Sven Schäfer
2010-05-07 20:58 ` console info objc
2010-05-08 6:28 ` AW: " Sven Schäfer
2010-05-08 10:03 ` Orm Finnendahl [this message]
2010-05-08 15:14 ` Thien-Thi Nguyen
2010-05-21 11:01 ` Andy Wingo
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=20100508100349.GB28863@varese \
--to=o.finnendahl@mh-freiburg.de \
--cc=guile-user@gnu.org \
--cc=sven-schaefer-ww@web.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).