From: Hongbo Zhang <bobzhang1988@gmail.com>
To: "Jérémie Dimino" <jeremie@dimino.org>, "Caml List" <caml-list@inria.fr>
Subject: [Caml-list] Re: [ANN] utop 1.2
Date: Sat, 04 Aug 2012 21:20:33 -0400 [thread overview]
Message-ID: <501DCA61.8060800@gmail.com> (raw)
In-Reply-To: <20120731080321.0708141c@locris.home>
On 7/31/12 2:03 AM, Jérémie Dimino wrote:
> Hi,
Greetings,
Just have a try for the utop and give it up. Here are some
difficulties that I came across, no complains, hope that will help
utop's next release.
a. dependency too much. To my limited knowledge, utop is a standalone
binary, dependency on lwt is a big problem, I never managed to install
it successfully on Mac(I did on my Linux box)
b. I still give a try. and grabed package react, try to install
react, but found that react even don't work with ocamlfind. I stop here.
(package react is just one file, dependency on react is not worth)
I know it would be convenient to use some package managers like Godi,
but I maintained my own fork of ocaml(I changed the ocaml's compiler
frequently, using Godi would bring a lot of pain).
It would be great if utop is a stand alone package, or , a utop.byte
is still fine. I have used otags.byte built on Linux, and copied to my
Mac, it works fine.
I never used utop(never succeeded :-( ) , but I guess it maybe
something like slime for lisp, hope this will help utop to gain more users.
Best -- Hongbo Zhang
>
> The utop team is happy to announce the release of utop 1.2, an
> improved toplevel for OCaml. You can download it at this url:
>
> https://forge.ocamlcore.org/frs/download.php/949/utop-1.2.tar.gz
>
> Important changes are:
>
> * utop now handles parsing/typing/compilation errors itself, this
> means a better highlighting and more importantly that errors are
> emphasized in the emacs mode. The style of errors can be controlled
> via the face "utop-error" in emacs and with the "error" resource of
> ~/.utoprc in the terminal.
>
> * a "Lwt_main.run" is automatically inserted for toplevel expressions
> of type "_ Lwt.t". For example, with the classic toplevel:
>
> # Lwt_io.printf "Hello, world!\n";;
> - : unit Lwt.t = <abstract>
>
> and with the new utop:
>
> # Lwt_io.printf "Hello, world!\n";;
> - : unit = ()
>
> This behavior can be disabled with "UTop.set_auto_run_lwt false".
>
> * many emacs mode fixes and improvements. It is now possible to
> complete a phrase in a tuareg/typerex buffer using the toplevel
> environment. You have to bind the function "utop-edit-complete" to a
> key for this feature to work, it is unbound by default.
>
> Here is the complete changelog:
>
> * ocaml 4.00 compatibility
> * prevent findlib from being initialized twice
> * better highlighting of errors
> * automatically insert Lwt_main.run for
> toplevel expressions of type 'a Lwt.t
> * better camlp4 support
> ** parse quotations and antiquotations to
> handle completion inside them
> ** better support revised syntax
> * emacs mode improvements
> ** various fixes
> ** highlight errors
> ** add a menu
> ** add interactive list of findlib packages
> ** packages can be pre-loaded via the file variable
> "utop-package-list"
> ** better tuareg integration
> ** typerex integration
> ** allow to complete using the toplevel environment
> in a tuareg buffer
> ** allow to change the utop command
> ** use the same history as the terminal mode
> ** follow output of ocaml
>
> Enjoy!
>
next prev parent reply other threads:[~2012-08-05 1:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 6:03 [Caml-list] " Jérémie Dimino
2012-08-05 1:20 ` Hongbo Zhang [this message]
2012-08-05 2:47 ` [Caml-list] " Edgar Friendly
2012-08-05 9:25 ` Hongbo Zhang
2012-08-05 12:45 ` Daniel Bünzli
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=501DCA61.8060800@gmail.com \
--to=bobzhang1988@gmail.com \
--cc=caml-list@inria.fr \
--cc=jeremie@dimino.org \
/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