caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Xavier Clerc <xavier.clerc@inria.fr>
Cc: Francois Berenger <berenger@riken.jp>, OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamlbuild generates .annot files in _build
Date: Tue, 17 Jul 2012 09:49:16 +0100	[thread overview]
Message-ID: <789025DD-73B1-447D-8BF7-F08920164F9C@recoil.org> (raw)
In-Reply-To: <1648915031.12109301.1342508158790.JavaMail.root@inria.fr>

On 17 Jul 2012, at 07:55, Xavier Clerc wrote:
> 
> For the record, we already have a PR related to this problem:
>  http://caml.inria.fr/mantis/view.php?id=5226
> 
> As you can see there, we have not reached consensus about
> what to do. However, following the ocamlbuild philosophy
> of leaving the source directories untouched and thus to
> produce all files in a build directory, we incline to think
> that the problem should be handled in the tools accessing
> annotation files.

The ocaml-annot tool is an external command that integrates
with pretty much any editor, and looks in multiple locations for
the .annot file (pwd, _build, among others).
https://github.com/avsm/ocaml-annot

Works great for me, as it's pretty much the only fancy editor
thing I use (although that's likely to change with the forthcoming
binannot feature in 4.00!).

-anil

  parent reply	other threads:[~2012-07-17  8:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17  5:12 Francois Berenger
2012-07-17  5:25 ` Francois Berenger
2012-07-17  7:00   ` Xavier Clerc
2012-07-17  7:35     ` Francois Berenger
2012-07-17 14:46     ` Romain Bardou
2012-07-17  6:55 ` Xavier Clerc
2012-07-17  7:24   ` Francois Berenger
2012-07-17  7:27     ` Francois Berenger
2012-07-17  7:31     ` Xavier Clerc
2012-07-17 14:28       ` Romain Bardou
2012-07-17  8:49   ` Anil Madhavapeddy [this message]
2012-07-17 11:05 ` Daniel Bünzli

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=789025DD-73B1-447D-8BF7-F08920164F9C@recoil.org \
    --to=anil@recoil.org \
    --cc=berenger@riken.jp \
    --cc=caml-list@inria.fr \
    --cc=xavier.clerc@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).