caml-list - the Caml user's mailing list
 help / Atom feed
From: "Soegtrop, Michael" <>
To: "" <>
Subject: [Caml-list] Opam env hook obscurities
Date: Wed, 1 May 2019 20:52:37 +0000
Message-ID: <> (raw)

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

Dear Opam Team,

first let me say that I am using the Cygwin MinGW cross opam from

I have the call to .opam/opam-init/ in my .bach_profile file.

I observe two obscurities with this setup:

1.)    It is really hard to get rid of the opam path settings, I guess cause of the environment hook installed. E.g. although opam env -revert displays the correct original "pre opam" PATH, evaluating with eval $(opam env -revert) does not have the desired effect - the PATH is exactly as before. I guess the environment hook immediately sets it back it. How can I temporarily get back to my original PATH?

2.)    Apparently the MANPATH gets longer each time I execute a command in bash. E.g. when I do a few times "echo $MANPATH | wc" the length displayed by wc increases each time (by one additional reference to the opam man path). This is unfortunate because the total environment of a process is quite limited under Cygwin/windows (I think to 8k).

Is this specific to the MinGW cross opam or is this a general problem?

Do others have the call to .opam/opam-init/ in there profile or a simple eval $(opam env)? What is the advantage of this rather invasive hook?

Best regards,

Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0,
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

[-- Attachment #2: Type: text/html, Size: 6168 bytes --]

                 reply index

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

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

caml-list - the Caml user's mailing list

Archives are clonable: git clone --mirror

AGPL code for this site: git clone public-inbox