caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: blue storm <bluestorm.dylc@gmail.com>
To: Sam Steingold <sds@gnu.org>
Cc: caml-list@yquem.inria.fr, tuareg-mode@googlegroups.com
Subject: Re: [Caml-list] new emacs tuareg mode release
Date: Mon, 24 May 2010 22:34:33 +0200	[thread overview]
Message-ID: <AANLkTim5t-mFmc_D4-xSYF2FsPyBdOA3LweR7b_-b8IM@mail.gmail.com> (raw)
In-Reply-To: <4BFAAB04.40906@gnu.org>

I have long used the emacs tuareg mode (simply because when I asked
advice someone told me that it was better than the standard caml
mode), and have recently wondered if that choice was motivated by
rational reasons. When I looked at it, I discovered that the original
caml mode has overall the same set of features (with some of them
coming earlier due to it being maintained by the OCaml team), was
reasonably well documented and was split in multiple source files
instead of one monolithic .el for tuareg-mode. I switched to the
standard caml-mode. The indentation, coloring and shorctuts are a bit
different, but otherwise I don't see what motivated the better tuareg
reputation.

Are you planning to add new features that would make tuareg decisively
better ? Have I missed some existing killer feature ? Why did you
choose to maintain the tuareg mode instead of collaborating with the
caml-mode upstream ?


  parent reply	other threads:[~2010-05-24 20:34 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 ` blue storm [this message]
2010-05-26 10:02   ` [Caml-list] new emacs tuareg mode release Tom Hutchinson
2010-05-26 13:18     ` Eliot Handelman
2010-05-26 13:32       ` Jacques Garrigue
2010-05-26 13:33     ` Mehdi Dogguy
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=AANLkTim5t-mFmc_D4-xSYF2FsPyBdOA3LweR7b_-b8IM@mail.gmail.com \
    --to=bluestorm.dylc@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=sds@gnu.org \
    --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;
as well as URLs for NNTP newsgroup(s).