From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Jun Furuse <jun.furuse@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Jump-to-definition and type-aware completion for Caml (was : Argot 1.0 release)
Date: Fri, 4 Nov 2011 20:49:22 +0100 [thread overview]
Message-ID: <CALgo1QJDK4dS9_A+czFiDLVUp20D90FhGZe8uvWCynLWzmRtQQ@mail.gmail.com> (raw)
In-Reply-To: <CAAoLEWt2obc9vOLbyzXsOfnpVim18pib_dD5GN7KeKfcXS=4yw@mail.gmail.com>
> If you do not trust me (and you should not :-) )
I trust no one anyway... The problem is more what Gabriel perfectly
captured by :
> Beware that all those projects tend to be built as patches to the
> ocaml distribution, which means difficult deployment (which means few
> users, which means few maintenance, which means bitrot).
Best,
Daniel
prev parent reply other threads:[~2011-11-04 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 12:39 [Caml-list] " Gabriel Scherer
2011-11-04 13:21 ` [Caml-list] " Daniel Bünzli
2011-11-04 16:53 ` Yaron Minsky
2011-11-04 18:37 ` Jun Furuse
2011-11-04 19:49 ` Daniel Bünzli [this message]
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=CALgo1QJDK4dS9_A+czFiDLVUp20D90FhGZe8uvWCynLWzmRtQQ@mail.gmail.com \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=jun.furuse@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