From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 398F97EE25 for ; Sat, 15 Jun 2013 17:14:39 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of anil@recoil.org) identity=pra; client-ip=89.16.177.154; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="anil@recoil.org"; x-sender="anil@recoil.org"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of anil@recoil.org) identity=mailfrom; client-ip=89.16.177.154; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="anil@recoil.org"; x-sender="anil@recoil.org"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@dark.recoil.org) identity=helo; client-ip=89.16.177.154; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="anil@recoil.org"; x-sender="postmaster@dark.recoil.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArkDAF6DvFFZELGadGdsb2JhbABagzqsapIigRsOAQwVCDyCIwEBAQMBAQEBawsFCwsYDSEhBgEdEgYTEgmHYQMJCgiwRgMKiFKMZIIyMweCf2EDlHxegWeBKYp2iDQ7 X-IPAS-Result: ArkDAF6DvFFZELGadGdsb2JhbABagzqsapIigRsOAQwVCDyCIwEBAQMBAQEBawsFCwsYDSEhBgEdEgYTEgmHYQMJCgiwRgMKiFKMZIIyMweCf2EDlHxegWeBKYp2iDQ7 X-IronPort-AV: E=Sophos;i="4.87,872,1363129200"; d="scan'208";a="17910976" Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) ([89.16.177.154]) by mail3-smtp-sop.national.inria.fr with SMTP; 15 Jun 2013 17:14:38 +0200 Received: (qmail 5243 invoked by uid 634); 15 Jun 2013 15:14:37 -0000 X-Spam-Level: * X-Spam-Check-By: dark.recoil.org Received: from host86-162-158-144.range86-162.btcentralplus.com (HELO [10.10.42.58]) (86.162.158.144) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 15 Jun 2013 16:14:36 +0100 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 15 Jun 2013 16:14:35 +0100 Cc: caml users , Leo White , ivg@ieee.org, opam-devel@lists.ocaml.org, Christophe TROESTLER , Wojciech Meyer Content-Transfer-Encoding: quoted-printable Message-Id: References: <87li6z8x0m.fsf@ieee.org> <20130528.102112.1182989008075506917.Christophe.Troestler@umons.ac.be> <878v2qj57l.fsf@kingston.cl.cam.ac.uk> To: Gabriel Scherer X-Mailer: Apple Mail (2.1503) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: Re: [opam-devel] [Caml-list] Setting up OPAM in emacs I don't use Emacs, but OPAM has several global command-line options that may make your OS^H^Heditor integration easier. * --root will set the home directory of OPAM (~/.opam by default) * --switch will explicitly run the command under a compiler switch that isn't the default one, but without performing a global switch. * "opam config exec" will run the sub-command with the right environment variables set to the selected switch. So: $ opam config exec "ocamlc -version" will get the version of the current OPAM switch ocaml, irrespective of your PATH settings. (This is what Leo is doing for his interactive shell below, but I'm not sure how this interacts with the rest of=20 Tuareg). I would appreciate an Emacs user summarising best practises here and letting me know so that I can include a short summary in Real World OCaml. best, Anil On 15 Jun 2013, at 13:07, Gabriel Scherer wrote: > I don't (want to) understand the details of why opam switches don't > work well with Emacs right now, or of any of the proposed solutions. > Is there a solution integrated in OPAM by now? If not, is there a > consensus on what simple users like me should use to solve the > problem? Could you (the thread participants) decide on something, and > send that to the OPAM upstream, so that future versions solve this > issue? >=20 > (The immediate problem I observe is that compile-command does not use > the OCaml versions I would expect it to, in general defaulting to my > system OCaml -- that may depend on the way Emacs is launched. More > sophisticated things such as being able to call "opam switch" from > inside Emacs are probably secondary needs, and I would be fine with a > basic integration not supporting that, and letting people hone their > emacs-lisp skills for that.) >=20 > On Tue, Jun 4, 2013 at 4:55 PM, Leo White wrote: >> My personal solution for Tuareg mode is to put: >>=20 >> ;; Use OPAM's ocaml >> (setq tuareg-interactive-program "opam config exec ocaml") >>=20 >> in my .emacs. >>=20 >> Regards, >>=20 >> Leo >>=20 >> Wojciech Meyer writes: >>=20 >>> Christophe's function hook is probably much better and elegant solution, >>> but this works for me: >>>=20 >>>>>=20 >>> (defun dm-opam-switch-root (ocaml-version opam-root) >>> (interactive "sOCaml version: \nsOPAM root: ") >>> (let* ((path (if (string-match "\\.opam" (car exec-path)) (cdr exec-pa= th) exec-path)) >>> (entry >>> (replace-regexp-in-string >>> "\n" "" >>> (shell-command-to-string >>> (format "opam switch --root %s %s > /dev/null && opam config= env | sed -n 's/^PATH=3D\\([^:]\\+\\):.*$/\\1/p'" opam-root ocaml-version)= ))) >>> (env-path (replace-regexp-in-string "\n" "" (shell-command-to-s= tring (format "opam config env --root %s | sed -n 's/^PATH=3D\\(.*\\)/\\1/p= '" opam-root))))) >>> (setq exec-path (cons entry path)) >>> (setenv "PATH" env-path))) >>>=20 >>> (defun dm-opam-switch (ocaml-version) >>> (interactive "sOCaml version: ") >>> (dm-opam-switch-root ocaml-version "~/.opam")) >>> << >>>=20 >>> I wouldn't say myself it's a perfect script, but it works. Note that I >>> use a lot of shell trickery instead of Emacs buffers, which is probably >>> not a good idea. >>>=20 >>> You just say M-x dm-opam-switch, and indicate which version you would >>> like. >>>=20 >>> Best, >>> Wojciech >>>=20 >>> Christophe TROESTLER writes: >>>=20 >>>> On Tue, 28 May 2013 09:59:53 +0400, Ivan Gotovchits wrote: >>>>>=20 >>>>> 2. Use =ABeval `opam env config`=BB in the begining of a compile-comm= and. >>>>> This works fine when you switch compiler, but other commands, such = as >>>>> =ABC-c C-s=BB doesn't use new environment. >>>>=20 >>>> I use this for the compilation: >>>>=20 >>>> ;; OPAM compilation =97 one must update to the current compiler >>>> ;; before launching the compilation. >>>> (defadvice compile (before compile-opam activate) >>>> "Run opam to update environment variables" >>>> (set (make-local-variable 'compilation-environment) >>>> (with-temp-buffer >>>> (ignore-errors (call-process "opam" nil t nil "config" "-env"= )) >>>> (goto-char (point-min)) >>>> (while (re-search-forward "; *export.*$" nil t) >>>> (replace-match "" nil nil)) >>>> (split-string (buffer-substring 1 (point-max))) >>>> ))) >>>>=20 >>>> For the toplevel, I am afraid one needs to restart it. I guess a >>>> similar trick is possible to automatically select the right one. >>>>=20 >>>> Hope it helps, >>>> C. >>=20 >> -- >> 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 > _______________________________________________ > opam-devel mailing list > opam-devel@lists.ocaml.org > http://lists.ocaml.org/listinfo/opam-devel >=20