[opam-devel] Opam 1.2 breaks emacs on the mac sortof

[Yaron Minsky]

Hmm.  I just tried your elisp code, and it doesn't quite get me there.
In particular, compilation now looks fine, but utop and merlin no
longer work, because emacs can no longer find them.  In particular, by
not extending exec-path, you lose the ability to directly invoke those
commands.  Also, a shell buffer (created with M-x shell) has the wrong
path, i.e., the path without opam putting its stuff in.  Maybe I
should put the opam stuff in the .bashrc.

Do those things work properly for you?

y

On Tue, Sep 9, 2014 at 8:21 AM, Daniel Bünzli
<daniel.buenzli at erratique.ch> wrote:
> Le mardi, 9 septembre 2014 à 13:11, Yaron Minsky a écrit :
>> Can someone confirm that the change in how "opam config env" really
>> happened between 1.1.2 and 1.2?
>
> Could you exhibit a sample invocation showing the problem ? I do use the
>
> (setq shell-command-switch "-lc")
>
> trick. But none of the other things except a
>
> (add-to-list 'load-path
>  (concat
>   (replace-regexp-in-string "\n$" ""
>   (shell-command-to-string "opam config var share"))
>   "/emacs/site-lisp"))
>
>
>
> and things don't break here, at least in compilation mode.
>
> If I switch and try an `ocamlc -version` I get the correct ocamlc invoked. I suspect you should drop that `opam config env —sexp` thing aswell as updating the exec-path. These things are only going to be invoked once and thus will not adapt to the current switch (as won't the above addition to 'load-path).
>
> Best,
>
> Daniel
>
>
> _______________________________________________
> opam-devel mailing list
> opam-devel at lists.ocaml.org
> http://lists.ocaml.org/listinfo/opam-devel