From: Allan Wegan <allanwegan@allanwegan.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] IDE like PyCharm - Results
Date: Tue, 10 May 2016 23:04:32 +0200 [thread overview]
Message-ID: <57324CE0.5040006@allanwegan.de> (raw)
In-Reply-To: <572FBB68.1010506@allanwegan.de>
[-- Attachment #1: Type: text/plain, Size: 1925 bytes --]
I checked the results of this thread and from my point of view, that are
the results:
emacs:
Already got two operating systems to use and don't want to learn another
one. I know, you all *love* this beast. But i have used Windows for a
long time before i switched to Gentoo. I just can't live without a
usable GUI anymore.
Atom editor with Nuclide extension:
$ opam install merlin ocamlbuild ocp-indent
-> installed some stuff
$ apm install nuclide language-ocaml ocaml-indent build
-> "bash: apm: command not found"
OCaml-top:
Single file solution - not really an IDE but still better than Scite
(that i used until now) - so i tried to use that...
...but it failed with complaining about missing lablgtk2 (wich
definitely is installed) on executing ocp-build to build it.
https://try.ocamlpro.com/:
Nice tutorial and will use it - but it is not an IDE.
OcaIDE:
Looks dead and installing Eclipse would probably lead to nightmares.
OCamlEditor:
Looks good and i surely want to use it...
...but it failed with complaining about missing lablgtk2 (wich
definitely is installed) on executing "ocaml build.ml ocamleditor" to
build it.
I think i somehow got into build environment hell. Is there any
*working* tutorial about how to properly set up the build environment
for OCamlEditor and/or OCaml-top?
I am also interested in other type-inferring (i love that concept)
statically typed functional non-lazy-evaluation (no Haskell please)
compiled languages - preferably one with a mature eco system (now that i
have experienced how important that is).
--
Allan Wegan
<http://www.allanwegan.de/>
Jabber: allanwegan@ffnord.net
OTR-Fingerprint: E4DCAA40 4859428E B3912896 F2498604 8CAA126F
Jabber: allanwegan@jabber.ccc.de
OTR-Fingerprint: A1AAA1B9 C067F988 4A424D33 98343469 29164587
ICQ: 209459114
OTR-Fingerprint: 71DE5B5E 67D6D758 A93BF1CE 7DA06625 205AC6EC
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-05-10 21:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 22:19 [Caml-list] IDE like PyCharm Allan Wegan
2016-05-09 8:08 ` Francois Berenger
2016-05-09 8:24 ` vrotaru.md
2016-05-09 9:44 ` Jean-Marc Alliot
2016-05-09 11:48 ` Ivan Gotovchits
2016-05-10 21:04 ` Allan Wegan [this message]
2016-05-10 21:57 ` [Caml-list] IDE like PyCharm - Results Benjamin Greenman
2016-05-10 23:16 ` Allan Wegan
2016-05-11 6:44 ` Vu Ngoc San
2016-05-10 22:08 ` Bahman Movaqar
2016-05-11 0:30 ` Allan Wegan
2016-05-11 6:16 ` David Allsopp
2016-05-11 6:51 ` vrotaru.md
2016-05-11 11:19 ` Allan Wegan
2016-05-11 11:23 ` Kakadu
2016-05-11 13:13 ` David Allsopp
2016-05-11 13:43 ` Hendrik Boom
2016-05-11 13:55 ` Ivan Gotovchits
2016-05-15 12:39 ` [Caml-list] Ocaml and Windows' notion of Unicode file names Andreas Rossberg
2016-05-15 16:42 ` Adrien Nader
2016-05-16 7:30 ` Matthieu Dubuget
2016-05-17 13:01 ` rossberg
2016-05-11 6:54 ` [Caml-list] IDE like PyCharm - Results Leonardo Laguna Ruiz
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=57324CE0.5040006@allanwegan.de \
--to=allanwegan@allanwegan.de \
--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