From: Ken Raeburn <raeburn@raeburn.org>
To: guile-emacs@sourceware.cygnus.com
Subject: Re: interrupting the Scheme process
Date: Sat, 06 May 2000 10:34:00 -0000 [thread overview]
Message-ID: <200005061734.NAA13088@raeburn.org> (raw)
In-Reply-To: <m3em7fu3j9.fsf@kei.cwru.edu>
Keisuke Nishida <kxn30@po.cwru.edu> writes:
> It seems Emacs catches the interrupt by interrupt_signal in keyboard.c,
> so we could modify this function so that it also sets the Guile's flag.
> If this works, we can convert the signal from Guile into a Emacs's quit
> signal. In case this doesn't work, I don't know what to do.
Looks like the right place to start. Like I said, figuring out
which language should get the interrupt and how to propagate the
interrupt across language boundaries will probably be trickier than
figuring out where to set the flags.
> > I suppose we could have a "spawn and wait for multiple threads"
> > function which implements all of this on top of the scheme^Wplan you
> > describe, by trapping the interrupt...
>
> Anyway, we can't work on this until your Guile-based Emacs appears :)
Yeah.... Emacs 21.1 is going into feature freeze soon, so it's a good
time for me to stop putting changes into it and focus on merging it
back into my guile-emacs source base. Then when the final release
comes, I should be able to make diffs available rather quickly.
Ken
prev parent reply other threads:[~2000-05-06 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-03 4:52 scheme directory Satoru Takabayashi
2000-05-03 12:15 ` Kalle Olavi Niemitalo
2000-05-05 11:56 ` Ken Raeburn
2000-05-03 15:03 ` interrupting the Scheme process Keisuke Nishida
2000-05-04 10:21 ` Kalle Olavi Niemitalo
2000-05-05 12:08 ` Ken Raeburn
2000-05-06 8:00 ` Keisuke Nishida
2000-05-06 10:34 ` Ken Raeburn [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200005061734.NAA13088@raeburn.org \
--to=raeburn@raeburn.org \
--cc=guile-emacs@sourceware.cygnus.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).