From: Louis Gesbert <louis.gesbert@ocamlpro.com>
To: caml-list@inria.fr, "Raphaël Proust" <raphlalou@gmail.com>
Cc: "François Bobot" <francois.bobot@cea.fr>
Subject: Re: [Caml-list] Merlin question about configuration file
Date: Fri, 15 Nov 2013 14:51:40 +0100 [thread overview]
Message-ID: <1783206.VOne7zSJ3k@agaric> (raw)
In-Reply-To: <CAAmHUAmdNNevi4TQj+5swcbTOh-2-QYZ2wOrO818iXpd7i-unA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 958 bytes --]
Le vendredi 15 novembre 2013 13:35:19 Raphaël Proust a écrit :
> On Fri, Nov 15, 2013 at 1:26 PM, François Bobot <francois.bobot@cea.fr> wrote:
> > On 15/11/2013 13:52, Johan Mazel wrote:
> >> […]
> > There is another glitch if you have a big code base with many
> > sub-...-subdirectories: merlin look for the .merlin in the current directory
> > and the parent directory.[…]
>
> Maybe there should be an option for Merlin to look arbitrarily far
> into parent directories, stopping whenever a .git, .svn, _darcs, &c.
> is found. (This is generally a good indication that one is at the root
> of a project.)
>
> Does that make sense?
> Would that help?
>
That's what I do in ocp-index, a bit of a hack but quite handy, and I've not had problems with it so far. (As François points out, .svn is probably not a good idea though)
Implementation here: https://github.com/OCamlPro/ocp-index/blob/master/src/indexOptions.ml#L62
[-- Attachment #2: Type: text/html, Size: 4359 bytes --]
next prev parent reply other threads:[~2013-11-15 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 12:52 Johan Mazel
2013-11-15 13:26 ` François Bobot
2013-11-15 13:35 ` Raphaël Proust
2013-11-15 13:48 ` François Bobot
[not found] ` <CAD5gH1HxcrbYR5MgK+jOwuxonJAKfTMHUwTAxG7XwOip4K3_dQ@mail.gmail.com>
2013-11-15 14:13 ` François Bobot
2013-11-16 1:58 ` Edgar Friendly
2013-11-16 9:52 ` Thomas Refis
2013-11-15 13:51 ` Louis Gesbert [this message]
2013-11-16 9:55 ` 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=1783206.VOne7zSJ3k@agaric \
--to=louis.gesbert@ocamlpro.com \
--cc=caml-list@inria.fr \
--cc=francois.bobot@cea.fr \
--cc=raphlalou@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).