caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Igor Peshansky <pechtcha@cs.nyu.edu>
To: Jeremy Shute <shutej@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Tuareg mode under Cygwin...
Date: Mon, 20 Feb 2006 11:25:13 -0500 (EST)	[thread overview]
Message-ID: <Pine.GSO.4.63.0602201116090.18782@access1.cims.nyu.edu> (raw)
In-Reply-To: <8c64de0a0602190746x2056a24cke96da953baf76475@mail.gmail.com>

On Sun, 19 Feb 2006, Jeremy Shute wrote:

> Hi,
>
> When I fire up Tuareg mode under native Windows emacs and run an
> inferior-caml, I get what I expect (Caml running in an emacs buffer).
> When I do so with Cygwin's Emacs, I get an empty buffer and a process
> "ocamlrun.exe" dressed in new window trim, which seems completely
> detached from the inferior-caml buffer (meaning C-c C-e does NOT send
> commands to this new process).
>
> I asked Albert Cohen, Tuareg-mode's creator, but he didn't know much
> about Windows, and suggested I ask here.
>
> What magic Elisp incantation will shackle invocations of "ocaml" in a
> buffer, when using Cygwin emacs?  I also tried "sh -c ocaml" to no
> avail...
>
> Jeremy

Hi, Jeremy,

This sounds like either a Cygwin emacs bug or a bug in the commands Tuareg
uses to start the ocaml process that manifests only in Cygwin's emacs.
Since this is likely not a problem with ocaml itself (but rather with
either the Cygwin ocaml package or Cygwin emacs), the main Cygwin list
(<cygwin at cygwin dot com>) would be a better place to discuss it and
track down the culprit.

Unfortunately, I don't use emacs, and haven't tested the Cygwin O'Caml
package under emacs (and wouldn't know how).  Thus, another reason to move
this to the main Cygwin list, since there are many emacs experts there.

One thing that would help is following the Cygwin problem reporting
guidelines at <http://cygwin.com/problems.html> when re-posting this to
the main Cygwin list (particularly attaching the output of "cygcheck
-svr").

See you on the Cygwin list, :-)

Igor Peshansky, the Cygwin O'Caml volunteer maintainer
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"


  reply	other threads:[~2006-02-20 16:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 15:46 Jeremy Shute
2006-02-20 16:25 ` Igor Peshansky [this message]
2006-02-20 17:08   ` [Caml-list] " Matthieu Dubuget
2006-02-20 17:19     ` Igor Peshansky
2006-02-20 19:10       ` Matthieu Dubuget
2006-02-20 22:38         ` Igor Peshansky
2006-02-21  1:39           ` Jeremy Shute
2006-02-21  2:31             ` Igor Peshansky
2006-02-21  2:55               ` Jeremy Shute
2006-02-21 14:38                 ` Igor Peshansky

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=Pine.GSO.4.63.0602201116090.18782@access1.cims.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=caml-list@yquem.inria.fr \
    --cc=shutej@gmail.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 NNTP newsgroup(s).