home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!corton!loria!news.loria.fr!bosch
- From: bosch@loria.fr (Guido Bosch)
- Newsgroups: alt.lucid-emacs.help
- Subject: Re: Ilisp: interrupting the inferior lisp process
- Message-ID: <BOSCH.92Jul26232738@moebius.loria.fr>
- Date: 26 Jul 92 21:27:38 GMT
- References: <1992Jul23.165340.15396@jpl-devvax.jpl.nasa.gov>
- Sender: news@news.loria.fr
- Followup-To: alt.lucid-emacs.help
- Organization: INRIA-Lorraine / CRIN, Nancy, France
- Lines: 30
- In-reply-to: rouquett@Aig.Jpl.Nasa.Gov's message of 23 Jul 92 16:53:40 GMT
-
- In article <1992Jul23.165340.15396@jpl-devvax.jpl.nasa.gov> rouquett@Aig.Jpl.Nasa.Gov (Nicolas Rouquette) writes:
- > THere seems to be a problem with Ilisp: both interrupt-subjob-ilisp
- > and reset-ilisp don't affect the inferior ilisp process at all.
- > Has anyone encountered this or is there a known workaround?
- >
- > This occurs with lemacs 19.1 with binaries from lucid. We're running
- > both 4.1.1 and 4.1.2 and openwindows 3.0.
- >
-
- I don't have a fix, but some more details on that problem:
-
- The elisp function `interrupt-process' does not work correctly if the
- process to interrupt uses pipes for the comunication with Emacs (this
- happens if the variable `process-connection-type' is nil at the moment
- Emacs starts an inferior process, as is the case for ILISP).
-
- The command `shell' uses a pty instead, and then `interrupt-process'
- seems to work.
-
- -- Guido
-
- --
- Guido BOSCH, INRIA-Lorraine/CRIN
- Institut National de Recherche en Informatique et en Automatique (INRIA)
- Centre de Recherche en Informatique de Nancy (CRIN)
- Campus scientifique, B.P. 239
- 54506 Vandoeuvre-les-Nancy CEDEX
- Tel.: (+33) 83.91.24.24
- Fax.: (+33) 83.41.30.79
- email: bosch@loria.fr
-