Hi Neil,
> > No, we didn't, although I agree such a parameter would be pretty
> > useful.
>
> Well we discussed it a bit here:
> http://lists.gnu.org/archive/html/guile-devel/2008-02/msg4.html
> http://lists.gnu.org/archive/html/guile-devel/2008-02/msg5.html
Argh, don't know how I m
Neil Jerram <[EMAIL PROTECTED]> writes:
> Andy Wingo <[EMAIL PROTECTED]> writes:
>
>> Then reassociate that buffer with the new process, and try evaluating
>> the above form. For me, GDS goes into the "running" state and never
>> comes back. To fix you have to kill the guile, kill the debug server
Andy Wingo <[EMAIL PROTECTED]> writes:
> Hello,
Hi Andy,
> It took me a while to isolate, but GDS has a problem when evaluating
> code that changes the current input port. For example, evaluate the
> following:
>
> (with-input-from-string "(+ 2 3)" read)
>
> If you are running with a "utility
"Julian Graham" <[EMAIL PROTECTED]> writes:
>> > @c begin (texi-doc-string "guile" "join-thread")
>> > [EMAIL PROTECTED] {Scheme Procedure} join-thread thread
>> > [EMAIL PROTECTED] {Scheme Procedure} join-thread thread [timeout]
>> > @deffnx {C Function} scm_join_thread (thread)
>> > [EMAIL PRO
Hello,
It took me a while to isolate, but GDS has a problem when evaluating
code that changes the current input port. For example, evaluate the
following:
(with-input-from-string "(+ 2 3)" read)
If you are running with a "utility guile", this should work. However, if
you start up another guile
