Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Mehdi Dogguy <mehdi.dogguy@pps.jussieu.fr>
To: Tom Hutchinson <thomas.hutchinson@sophia.inria.fr>
Cc: blue storm <bluestorm.dylc@gmail.com>,
	tuareg-mode@googlegroups.com, caml-list@yquem.inria.fr,
	Sam Steingold <sds@gnu.org>
Subject: Re: [Caml-list] new emacs tuareg mode release
Date: Wed, 26 May 2010 15:33:13 +0200	[thread overview]
Message-ID: <4BFD2319.7000702@pps.jussieu.fr> (raw)
In-Reply-To: <ACF6E28A-52C8-4068-A8A3-589D40FB19CE@sophia.inria.fr>

On 26/05/2010 12:02, Tom Hutchinson wrote:
> I would be most interested to hear answers to this e-mail.
> 

Me too. It would be nice if tuareg's upstream could summarize some points
to show the difference. That would help!

> I too have wondered about the differences between tuareg mode and caml 
> mode.
> 

I use only two features in tuareg-mode which are syntax coloring and
indentation (and from time to time, caml-show-types from caml-mode when
debugging). So my remarks (below) might not be complete but should be
enough (IMHO) for most of users to get an idea of the difference (for a
daily use):

- colors:

  * caml-mode doesn't colorize mll files as good as tuareg-mode: open any
    .mll file and look at any "rule foo bar = parse", it's all black. rules
    are functions, so they should be colorized the same way.
  * in caml-mode, functions and arguments have the same colors (when
    defining functions).
  * some operators are not colorized in caml-mode (e.g. "::"). I didn't
    check all of them, only "::"… but that's enough for me to not use
    caml-mode because, visually, "a::b" looks like a single block and
    might be harder to read (or to detect the structure when the expression
    if more complicated), which is not very nice.

  * in tuareg-mode 2.0, "let" and "open" statements (and some others) are
    bold and blue. I found that change quite surprising. It keeps my eyes
    clipped on them. They contrast too much with the other colors used.
  * in tuareg-mode 2.0, in mll files, rules are now harder to read because
    it uses mainly red (for symbols, let's say) and light brown for strings
    (as usual) and the contrast between these two colors is too low. It
    used to be dark purple and light brown which is (not perfect, but at
    least)a better default setting, IMHO.

  * For mly files, they provide almost the same coloring.

- indentation: they simply have different defaults. caml-mode sticks to
  the recommendations listed on ocaml's website, AFAIK, which is nice.
  Indentation is configurable in both modes and is a matter of taste.

- other features (ocamldebug, toplevel, …): almost the same, but with
  different names. Maybe there are some tiny differences here, but they
  don't pop up.

It might obvious for some people but, apparently, maybe not for who set
the new default colors, but syntax coloring is used to show in a *clear*
way the structure of the code. From what I see, they both fail to provide
a good syntax coloring. tuareg-mode 1.xx used to have better defaults.

Some people might consider my remarks as nipticking, and I can understand
that (since I can change these settings). But, tuareg-mode used to have
good defaults and failing at such a basic features for such a program is
completely crazy. Besides, I appreciate the efforts done from both sides and
I hope that they'll get better soon.

Regards,

-- 
Mehdi Dogguy مهدي الدڤي
http://www.pps.jussieu.fr/~dogguy


  parent reply	other threads:[~2010-05-26 13:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 16:36 Sam Steingold
2010-05-24 16:55 ` [Caml-list] " Stéphane Glondu
2010-05-24 17:17   ` Sam Steingold
2010-05-24 18:41 ` Philip
2010-05-24 20:09   ` Sam Steingold
2010-05-24 20:36     ` Philip
2010-05-24 20:58       ` Sam Steingold
2010-05-25  1:00         ` Eliot Handelman
2010-05-25 10:17           ` Jan Rehders
2010-05-25 18:04           ` Sam Steingold
2010-05-26  6:27             ` Stéphane Glondu
2010-05-26 13:33               ` Sam Steingold
2010-05-26 14:31             ` New emacs tuareg mode Christophe TROESTLER
2010-05-26 15:36               ` [Caml-list] " Daniel Bünzli
2010-05-26 16:01                 ` Christophe TROESTLER
2010-05-26 16:34                   ` Stefano Zacchiroli
2010-05-27  9:46               ` David Baelde
2010-05-27 14:25                 ` Eray Ozkural
2010-05-27 15:41                   ` Grant Rettke
2010-05-27 16:01                 ` Edgar Friendly
2010-05-29 13:16                   ` David Baelde
2010-05-24 20:34 ` [Caml-list] new emacs tuareg mode release blue storm
2010-05-26 10:02   ` Tom Hutchinson
2010-05-26 13:18     ` Eliot Handelman
2010-05-26 13:32       ` Jacques Garrigue
2010-05-26 13:33     ` Mehdi Dogguy [this message]
2010-05-26 14:01       ` Christophe TROESTLER
2010-05-26 14:09         ` Mehdi Dogguy
2010-05-24 21:44 ` Sam Steingold
2010-05-25 18:08   ` [Caml-list] " Mehdi Dogguy
2010-05-25 18:25     ` Christophe TROESTLER
2010-05-24 21:50 ` Sam Steingold
2010-05-26 22:53 ` Sam Steingold
2010-06-11 12:22 ` [Caml-list] " Albert Cohen

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=4BFD2319.7000702@pps.jussieu.fr \
    --to=mehdi.dogguy@pps.jussieu.fr \
    --cc=bluestorm.dylc@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=sds@gnu.org \
    --cc=thomas.hutchinson@sophia.inria.fr \
    --cc=tuareg-mode@googlegroups.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