caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Johan Mazel <johan.mazel@gmail.com>
To: Siraaj Khandkar <siraaj@khandkar.net>
Cc: Casey Basichis <caseybasichis@gmail.com>,
	romerun@gmail.com,  OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Setting up OcaIDE
Date: Thu, 22 Aug 2013 12:20:18 +0900	[thread overview]
Message-ID: <CAKS5mhRjZw2Q=9oyaTWdn0tKHU7kxXhaVzp+JS2mFqMfaXg1rw@mail.gmail.com> (raw)
In-Reply-To: <5214E8F1.7030200@khandkar.net>

[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]

Personally, I use OcaIDE but I use "Makefile project" and I manage my
compilation with oasis. Inside the Makefile, I call the oasis
configuration/compilation.
This (sometimes) create some problems when I want to open function
definition. The opened file is often the one in ./_build/src instead of
./src but, otherwise everything is working fine.


2013/8/22 Siraaj Khandkar <siraaj@khandkar.net>

> On 08/21/2013 11:13 AM, Casey Basichis wrote:
>
>>
>> May I ask what you are using in place of Eclipse?
>>
>> I've never used emacs, but after several days trying to get Eclipse to
>> work its learning curve is starting to look like a better use of time.
>>
>> What tools are folks commonly using to wrangle ocaml.  I'm on osx here,
>> if it makes any difference.
>>
>>
> I use Vim with omlet [1] and syntax file stolen from Marcus Mottl [2]. On
> both, Mac and Linux, but it doesn't make a difference :)
>
>
> [1]: http://www.vim.org/scripts/**script.php?script_id=1196<http://www.vim.org/scripts/script.php?script_id=1196>
> [2]: https://bitbucket.org/mmottl/**vim-files/src/<https://bitbucket.org/mmottl/vim-files/src/>
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/**arc/caml-list<https://sympa.inria.fr/sympa/arc/caml-list>
> Beginner's list: http://groups.yahoo.com/group/**ocaml_beginners<http://groups.yahoo.com/group/ocaml_beginners>
> Bug reports: http://caml.inria.fr/bin/caml-**bugs<http://caml.inria.fr/bin/caml-bugs>
>

[-- Attachment #2: Type: text/html, Size: 2245 bytes --]

  reply	other threads:[~2013-08-22  3:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 18:37 Casey Basichis
2013-08-20 18:51 ` David Allsopp
2013-08-20 19:09 ` Thomas Gazagnaire
2013-08-20 20:23   ` Casey Basichis
2013-08-20 20:29     ` Jeremy Yallop
     [not found]     ` <20130820.223527.351659178592840423.Christophe.Troestler@umons.ac.be>
2013-08-20 21:20       ` Casey Basichis
2013-08-20 22:15         ` Leo White
2013-08-20 22:18           ` Casey Basichis
2013-08-20 22:46             ` Leo White
2013-08-21  0:16               ` Casey Basichis
2013-08-21  6:32                 ` Komtanoo Pinpimai
2013-08-21 15:13                   ` Casey Basichis
2013-08-21 16:10                     ` Ashish Agarwal
2013-08-21 16:21                     ` Siraaj Khandkar
2013-08-22  3:20                       ` Johan Mazel [this message]
2013-08-22 20:19                     ` William R

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='CAKS5mhRjZw2Q=9oyaTWdn0tKHU7kxXhaVzp+JS2mFqMfaXg1rw@mail.gmail.com' \
    --to=johan.mazel@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=caseybasichis@gmail.com \
    --cc=romerun@gmail.com \
    --cc=siraaj@khandkar.net \
    /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).