Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Wojciech Meyer <wojciech.meyer@gmail.com>
To: "Török Edwin" <edwin+ml-ocaml@etorok.net>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] ANN: Merlin 1.3 -- advanced Vim and Emacs editor modes
Date: Fri, 16 Aug 2013 17:26:14 +0100	[thread overview]
Message-ID: <CAOg1smDPRGVGwtOrd269J37NFr-RHBK4D7jXeukPdBizF+iwTg@mail.gmail.com> (raw)
In-Reply-To: <520E40A7.302@etorok.net>

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

On the related not if we decide to expose API for ocamlbuild, we might
extract the needed information easily for Merlin.


On Fri, Aug 16, 2013 at 4:09 PM, Török Edwin <edwin+ml-ocaml@etorok.net>wrote:

> On 08/16/2013 05:52 PM, Thomas Refis wrote:
> >
> > As Gabriel said : feedback of all kind is very welcome!
>
> Is it planned to support ocamlbuild or _oasis?
> i.e. if I have an _tags file to find out automatically what ocamlfind
> packages I use, and where my source files are without having to create a
> .merlin.
> Similarly for _oasis, could there be an _oasis plugin to automatically
> generate a .merlin?
>
>
> Best regards,
> --Edwin
>
>
> --
> 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: 1534 bytes --]

  reply	other threads:[~2013-08-16 16:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 10:48 Gabriel Scherer
2013-08-16 11:50 ` Lukasz Stafiniak
2013-08-16 11:53   ` Lukasz Stafiniak
2013-08-16 13:42 ` Paolo Donadeo
2013-08-16 14:52 ` Thomas Refis
2013-08-16 15:09   ` Török Edwin
2013-08-16 16:26     ` Wojciech Meyer [this message]
2013-08-16 16:33 ` David Allsopp
2013-08-16 16:44   ` Thomas Refis

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=CAOg1smDPRGVGwtOrd269J37NFr-RHBK4D7jXeukPdBizF+iwTg@mail.gmail.com \
    --to=wojciech.meyer@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=edwin+ml-ocaml@etorok.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