From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: guile-user@gnu.org
Subject: Re: Guile.el
Date: Tue, 28 Jul 2009 01:37:00 +0200 [thread overview]
Message-ID: <87fxch66lf.fsf@mithrandir.homeunix.net> (raw)
In-Reply-To: 87eis1davy.fsf@arudy.ossau.uklinux.net
Neil Jerram <neil@ossau.uklinux.net> writes:
> 2. Not relying on standard input and output for communication with the
> Guile process that is being debugged. I think this is important,
> because apps often use standard input and output for other things!
geiser is based on comint-mode, meaning (as i'm sure you know) that
reliance on input/ouput is very easy to get rid of: comint can handle
telnet connections transparently, so it's just a matter of launching a
remote repl on guile's side, without any change to the elisp code,
geiser's scheme support libraries. i've just been lazy writing the repl
server thing :)
jao
prev parent reply other threads:[~2009-07-27 23:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 12:46 Guile.el tbrooke
2009-06-29 18:40 ` Guile.el Neil Jerram
2009-06-29 19:59 ` Guile.el Tom Brooke
2009-06-29 20:02 ` Guile.el Andrew Bagdanov
2009-06-29 21:03 ` Guile.el Neil Jerram
2009-06-29 21:09 ` Guile.el Ludovic Courtès
2009-07-14 22:22 ` Guile.el Dmitry Dzhus
2009-07-27 22:22 ` Guile.el Neil Jerram
2009-07-27 23:37 ` Jose A. Ortega Ruiz [this message]
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=87fxch66lf.fsf@mithrandir.homeunix.net \
--to=jao@gnu.org \
--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).