From: Taylor Venable <taylor@metasyntax.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user@gnu.org
Subject: Re: Jumping back to REPL prompt on ^C
Date: Tue, 27 Jul 2010 17:16:28 -0400 [thread overview]
Message-ID: <AANLkTim5EaqDZCXdFgy-P2ZOugKXHosc3hGmKAFZFWQZ@mail.gmail.com> (raw)
In-Reply-To: <m3lj9kprzt.fsf@unquote.localdomain>
Hi Andy. Very sorry for the late reply, it's been a few weeks since I
caught up with the list.
On Fri, Jul 9, 2010 at 11:57 AM, Andy Wingo <wingo@pobox.com> wrote:
> On Thu 08 Jul 2010 21:31, Andy Wingo <wingo@pobox.com> writes:
>
>>>> Except *sometimes* when I hit ^C I ended up with an error that stops
>>>> the guile program completely, seemingly due to the readline library
>>>> that I've enabled in the REPL. When I simplify my test I'm able to
>>>> get the same fatal error all the time.
>>> [..]
>>>> In unknown file:
>>>> ?: 0 [catch-closure misc-error "%readline" "readline is not reentrant" () #f]
>>
>> You know, I've seen this on a couple occaisions. If you can find out how
>> to reproduce this I would be very interested.
>
> I believe I have quashed all of these. Let me know if you can still
> reproduce this with git.
I just rebuilt with the latest git and it seems to be working. I've
been using this as a test:
(call/cc (lambda (k) (sigaction SIGINT (lambda (_) (k))) (let loop () (loop))))
And then interrupting with ^C. I also tried using SIGQUIT and ^\ with
the same successful effect, so it looks like it works.
Many thanks!
--
Taylor C. Venable
http://metasyntax.net/
prev parent reply other threads:[~2010-07-27 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 23:15 Jumping back to REPL prompt on ^C Taylor Venable
2010-07-04 20:52 ` Neil Jerram
2010-07-08 19:31 ` Andy Wingo
2010-07-09 15:57 ` Andy Wingo
2010-07-27 21:16 ` Taylor Venable [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=AANLkTim5EaqDZCXdFgy-P2ZOugKXHosc3hGmKAFZFWQZ@mail.gmail.com \
--to=taylor@metasyntax.net \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.com \
/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).