caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] New Ocaml Plug-in for NetBeans
Date: Mon, 28 Jul 2008 20:25:53 +0100	[thread overview]
Message-ID: <200807282025.53720.jon@ffconsultancy.com> (raw)
In-Reply-To: <488E010C.6060606@naughtydog.com>

On Monday 28 July 2008 18:25:32 Pal-Kristian Engstad wrote:
> Richard Jones wrote:
> > I'm sure you know why, but because (a) it's a huge amount of work and
> > (b) the sort of people who can do the work already use emacs so they
> > don't need it.
>
> Actually, as a regular Emacs hacker myself, I checked out .NET's F#
> environment and I must confess that I was quite impressed. It is
> actually really neat. Instead of the usual edit, M-x compile, M-x
> next-error cycle, the code is compiled in the background creating
> "squigglies" under code that has errors. Using this and the
> Intelli-sense completion features is very nice and I wish we could have
> the equivalent under Emacs. (Of course, though those features still
> won't detract me from my everyday daily use of Emacs.) Perhaps some
> OCaml/Emacs hackers could work together on a system where emacs and the
> ocaml communicates better?

Indeed.

On a related note: what would people recommend as a good OCaml source code 
editor under Linux for someone who finds Emacs too archaic and Eclipse too 
slow?

Are there any other editors with type throwback (and maybe even error 
throwback)?

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e


  reply	other threads:[~2008-07-28 19:25 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 11:14 adonis28850
2008-07-23  8:42 ` hmf
2008-07-23  8:50   ` adonis28850
2008-07-25 23:56     ` Jon Harrop
2008-07-26  0:24       ` Erik de Castro Lopo
2008-07-26  2:57         ` Jon Harrop
2008-07-26 12:25           ` Romain Beauxis
2008-07-26  9:09       ` Richard Jones
2008-07-28 17:25         ` Pal-Kristian Engstad
2008-07-28 19:25           ` Jon Harrop [this message]
2008-07-26 18:12 ` adonis28850
2008-07-26  8:46 hmf
2008-08-20  6:29 ` Maxence Guesdon
2008-08-20 14:38   ` Richard Jones
2008-08-22  6:34     ` Maxence Guesdon
2008-08-20 16:32   ` Jon Harrop
2008-08-22  6:41     ` Maxence Guesdon
2008-09-07 23:31     ` Nathaniel Gray
2008-09-08  1:10       ` Jon Harrop
2008-09-09  5:31         ` Nathaniel Gray
2008-09-09  7:43           ` Jon Harrop
2008-09-09  7:50             ` Nathaniel Gray
2008-08-27 20:24   ` kirillkh
2008-09-02  6:49     ` Maxence Guesdon
2008-07-26  9:02 hmf
2008-07-26  9:19 ` Richard Jones
2008-07-28  9:58   ` Florian Hars
2008-07-26 10:03 ` Erik de Castro Lopo
2008-07-26 11:40   ` Jon Harrop
2008-07-26 12:07     ` Erik de Castro Lopo
2008-07-26 15:22       ` Jon Harrop
2008-07-29 14:16         ` Damien Doligez
2008-07-29 14:30           ` Lukasz Stafiniak
2008-07-29 18:01             ` Jean-Christophe Filliâtre
2008-09-07 21:39     ` Nathaniel Gray
2008-07-26 11:42 ` Jon Harrop
2008-07-26  9:18 hmf
2008-07-26  9:22 ` Richard Jones
2008-07-26 12:01 hmf
2008-07-26 12:25 ` Erik de Castro Lopo
2008-07-26 15:37   ` Jon Harrop
2008-07-26 12:44 hmf

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=200807282025.53720.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --cc=caml-list@inria.fr \
    /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).