From: Xavier Leroy <xavier.leroy@inria.fr>
To: Sean McLaughlin <seanmcl@cs.nyu.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] emacs cygwin ocaml interrupt
Date: Fri, 29 Aug 2003 17:38:32 +0200 [thread overview]
Message-ID: <20030829173832.B10551@pauillac.inria.fr> (raw)
In-Reply-To: <000a01c36d86$1127eba0$187c8e88@tomlaptop1>; from seanmcl@cs.nyu.edu on Thu, Aug 28, 2003 at 01:01:42PM -0400
> I'd like to use the cygwin build of ocaml through emacs. I'm using
> vanilla emacs and cygwin, with the shell connection cygwin-mount.el.
> For some reason, when I use the binary windows edition of ocaml, I can
> send ocaml interrupts through emacs with C-c C-c. With the cygwin built
> version, though, I can't get any interrupts to work. I tried sifting
> through the 21 different signals but couldn't find out what ocaml is
> doing with C-c C-c.
Win32 doesn't have an exact equivalent to Unix signals, so software
ported from Unix (such as Emacs and OCaml, as well as Cygwin itself)
do a best effort to emulate them, but that doesn't mean the emulations
work well together...
The native Windows port of OCaml goes to some length to trap the "ctrl-C"
and "ctrl-break" conditions (which can be generated at the keyboard or
programmatically) and turn them into SIGINT signals. Apparently,
Emacs generates the right conditions in reply to C-c C-c.
The Cygwin build just relies on the Cygwin runtime environment to
emulate Unix signals, and I have no idea on what Cygwin does exactly.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2003-08-29 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 17:01 Sean McLaughlin
2003-08-29 15:38 ` Xavier Leroy [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=20030829173832.B10551@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=seanmcl@cs.nyu.edu \
/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