From: Xavier Leroy <xavier.leroy@inria.fr>
To: Steve Harris <scharris@worldnet.att.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] pipe communication with toplevel
Date: Mon, 5 Aug 2002 11:40:51 +0200 [thread overview]
Message-ID: <20020805114051.A16714@pauillac.inria.fr> (raw)
In-Reply-To: <66CAE6AE-A768-11D6-A36A-003065A79338@worldnet.att.net>; from scharris@worldnet.att.net on Sun, Aug 04, 2002 at 12:09:49AM -0500
> I'm doing a graphical ocaml toplevel wrapper for OS X, it's working
> except when I type in bad syntax,
> then the ocaml toplevel background process that I'm communicating with
> quits or dies, I don't know why. I've got the toplevel's standard
> in,out, and error redirected to pipes that the graphical shell is using
> for communication with it. The session is fine until bad input is
> finally typed. Any ideas about why it quits like that?
> Is it checking isatty() or similar on stdin and deciding there's no
> human so better to just quit upon error?
There is no such checking in the Caml code for the toplevel.
However, the toplevel calls termcap or terminfo functions to try and
underline graphically the error. Maybe these functions have a bug?
Try setting the TERM variable to "dumb" or "none" before starting the
toplevel, e.g. launch it with
/bin/sh -c "TERM=dumb ocaml"
- 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
next prev parent reply other threads:[~2002-08-05 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 5:09 Steve Harris
2002-08-05 9:40 ` Xavier Leroy [this message]
2002-08-06 3:23 ` Steve Harris
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=20020805114051.A16714@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=scharris@worldnet.att.net \
/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).