caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Wojciech Meyer <wojciech.meyer@googlemail.com>
To: Edgar Friendly <thelema314@gmail.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml linting
Date: Sat, 17 Nov 2012 02:05:12 +0000	[thread overview]
Message-ID: <CAOg1smBWb-OBBym-4+eYQ-F0hmt-zMoCw-UjuCGiTUirf0zvnA@mail.gmail.com> (raw)
In-Reply-To: <50A6EBAD.8050204@gmail.com>

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

Hi,

In typerex there is an experimental extension that enables compilation in
background,called flymake.
With Omake, you can specify the -P flag, then it will keep polling for
inode events and rebuild what is needed.

On Saturday, November 17, 2012, Edgar Friendly <thelema314@gmail.com> wrote:
> I'm playing with Sublime Text 2, and find it has an interesting plugin to
do active linting of a program under development.  What's the set of
compiler options that will produce warnings/errors the quickest, for using
ocamlc to quickly check for syntax and maybe even type errors in a partial
program?  Does anyone already have a process for this under emacs, using
auto-recompile or other plugins?
>
> Thanks,
> E.
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

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

  reply	other threads:[~2012-11-17  2:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-17  1:43 Edgar Friendly
2012-11-17  2:05 ` Wojciech Meyer [this message]
2012-11-17  8:35 ` Török Edwin
2012-11-23 17:30 ` Philippe Wang

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=CAOg1smBWb-OBBym-4+eYQ-F0hmt-zMoCw-UjuCGiTUirf0zvnA@mail.gmail.com \
    --to=wojciech.meyer@googlemail.com \
    --cc=caml-list@inria.fr \
    --cc=thelema314@gmail.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).