* problem with new debugger
@ 2010-01-28 1:50 Jose A. Ortega Ruiz
2010-01-28 18:40 ` Andy Wingo
0 siblings, 1 reply; 2+ messages in thread
From: Jose A. Ortega Ruiz @ 2010-01-28 1:50 UTC (permalink / raw)
To: guile-devel
Hi,
in an Emacs comint buffer,
(with-output-to-string (lambda () (display "foo")))
works as expected. But
(with-output-to-string (lambda () (error "foo")))
blocks the prompt until C-d is sent (via C-c C-d) to the terminal, at
which point the debugger prompt (sans the explanatory prelude) pops up.
(My guess is that the explanation is going to somewhere unawares of the
underlying redirection of stdout/stderr setup by comint, but i'm most
probably wrong).
Geiser, who's trying to adapt to the brave new debugging world, is
unhappy about this state of affairs ;)
Thanks,
jao
--
If all else fails read the instructions. - Donald Knuth
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: problem with new debugger
2010-01-28 1:50 problem with new debugger Jose A. Ortega Ruiz
@ 2010-01-28 18:40 ` Andy Wingo
0 siblings, 0 replies; 2+ messages in thread
From: Andy Wingo @ 2010-01-28 18:40 UTC (permalink / raw)
To: Jose A. Ortega Ruiz; +Cc: guile-devel
Hello,
On Thu 28 Jan 2010 02:50, "Jose A. Ortega Ruiz" <jao@gnu.org> writes:
> (with-output-to-string (lambda () (error "foo")))
This also happens if you don't enable readline, via running with guile
-q. I'll check it out.
Andy
--
http://wingolog.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-01-28 18:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-01-28 1:50 problem with new debugger Jose A. Ortega Ruiz
2010-01-28 18:40 ` Andy Wingo
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).