caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Richard Jones <rich@annexia.org>
To: hmf@inescporto.pt
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] New Ocaml Plug-in for NetBeans
Date: Sat, 26 Jul 2008 10:19:35 +0100	[thread overview]
Message-ID: <20080726091935.GC24428@annexia.org> (raw)
In-Reply-To: <1217062966.488ae8367f0d2@webmail.inescporto.pt>

On Sat, Jul 26, 2008 at 10:02:46AM +0100, hmf@inescporto.pt wrote:
> In fact mastering emacs, vi, etc. with all those "modes" also
> requires a lot of work.

You miss the point that most Unix programmers already know emacs or vi
intimately.  I use emacs constantly -- even for writing this very
email, and I have been using emacs for nearly 20 years.  No
"mastering" is needed.

I've used IDEs a bit, but never particularly saw the point.  They seem
to just obscure the workings of the build process, and break the
editor, for no tangible gain.  Emacs can already print the type of an
expression when you hover over it, and can autocomplete symbols.  I've
to find an IDE that can edit email.

There are many problems with the Unix build process -- eg. the horrors
of autoconf/automake/libtool, and possibly better integration with
packaging.  Lack of an all-in-one graphical tool is not exactly high
on anyone's list.

Rich.

-- 
Richard Jones
Red Hat


  reply	other threads:[~2008-07-26  9:19 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-26  9:02 hmf
2008-07-26  9:19 ` Richard Jones [this message]
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-07-26 12:17     ` [off-topic] was " Richard Jones
2008-07-26 15:51       ` Jon Harrop
2008-09-07 21:39     ` Nathaniel Gray
2008-07-26 11:42 ` Jon Harrop
  -- strict thread matches above, loose matches on Subject: below --
2008-07-26 12:44 hmf
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  9:18 hmf
2008-07-26  9:22 ` Richard Jones
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-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
2008-07-26 18:12 ` adonis28850

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=20080726091935.GC24428@annexia.org \
    --to=rich@annexia.org \
    --cc=caml-list@inria.fr \
    --cc=hmf@inescporto.pt \
    /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).