unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "objc" <objcjohn@hotmail.com>
To: "Sven Schäfer" <sven-schaefer-ww@web.de>, guile-user@gnu.org
Subject: console info
Date: Fri, 7 May 2010 21:58:16 +0100	[thread overview]
Message-ID: <SNT127-DS37CA86BAC0BCD48828489C8F60@phx.gbl> (raw)
In-Reply-To: <CD8F2FCCFF074BC9ACC43B24DA002FB5@SvenPC>

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

Hi Sven,

I'm messing around with MS Windows right now...

One interesting way is 

"How to spawn console processes with redirected standard handles" 

sample code at :
http://support.microsoft.com/kb/190351

and it is quite a general solution for many applications (such as using guile with windows).

related :

Having a console with windows is easy to do, and VERY useful for writing debug info using a simple printf(). (compile with a -mconsole flag).

You could hack around your guile source of course ;O).

Hope this helps,

obj.


From: Sven Schäfer 
Sent: Friday, May 07, 2010 8:28 PM
To: guile-user@gnu.org 
Subject: (no subject)


Hello,

 

I'm new in this list and I use Guile for the first time.

I start Guile in a program written in C.

Is it possible to disable the output "guile>" at the standard output?

That means, when I start Guile there is no "guile>" in the command line but I can give instructions to the interpreter.

 

I hope somebody can help me with this problem.

 

[-- Attachment #2: Type: text/html, Size: 5006 bytes --]

  reply	other threads:[~2010-05-07 20:58 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 ` objc [this message]
2010-05-08  6:28   ` AW: console info Sven Schäfer
2010-05-08 10:03     ` Orm Finnendahl
2010-05-08 15:14     ` AW: " 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=SNT127-DS37CA86BAC0BCD48828489C8F60@phx.gbl \
    --to=objcjohn@hotmail.com \
    --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).