caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alain Frisch <alain@frisch.fr>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] Help wanted: adapt emacs mode to generate .annot from .cmt
Date: Tue, 06 Nov 2012 13:46:53 +0100	[thread overview]
Message-ID: <509906BD.6070303@frisch.fr> (raw)

Dear all,

Is there any emacs-lisp hacker around who would like to help with the 
following ticket?

   http://caml.inria.fr/mantis/view.php?id=5812

The goal is to adapt the OCaml emacs mode to have it automatically 
(re)generate the .annot file when needed, from the .cmt file, using the 
existing read_cmt tool.  This would allow to get rid of the -annot flag 
when compiling (it is much slower than -bin-annot) while keeping the 
same comfort in emacs.  (I know that better alternatives like TypeRex or 
ocamlspotter exist, but having the default emacs mode support .cmt files 
would still be very useful.)


Alain

                 reply	other threads:[~2012-11-06 12:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=509906BD.6070303@frisch.fr \
    --to=alain@frisch.fr \
    --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;
as well as URLs for NNTP newsgroup(s).