unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
Subject: Catching user interrupts
Date: Tue, 03 Feb 2004 16:39:10 +0200	[thread overview]
Message-ID: <1075819149.3257.237.camel@localhost> (raw)

Hi gang,

I'm running into trouble catching interrupts. It always works the first
time, but the second time I run a piece of code in the repl it becomes
unresponsive. For example:

(catch #t
       (lambda () (while #t #t))
       (lambda (key . args)
	 (if (not (eq? key 'signal))
	     (apply throw key args))))

Try that twice in your repl.

I've tried a lot more methods (sigaction throwing 'interrupt, sigaction
setting a system async to throw 'interrupt), but nothing works the
second time. Any clues? Thanks.
-- 
Andy Wingo <wingo@pobox.com>


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


             reply	other threads:[~2004-02-03 14:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 14:39 Andy Wingo [this message]
2004-03-20 22:08 ` Catching user interrupts Marius Vollmer

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=1075819149.3257.237.camel@localhost \
    --to=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).