From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Managing environments (Python venv, guix environment, etc.) Date: Sun, 24 Jul 2016 20:58:28 +0300 Message-ID: <834m7evry3.fsf@gnu.org> References: <87y453sy0n.fsf@earth.catern.com> <87r3arripr.fsf@earth.catern.com> <874m7jygot.fsf@earth.catern.com> <83oa5ox21u.fsf@gnu.org> <123d2ae9-b523-5d5b-3bf8-c6e4462270b8@yandex.ru> <87a8h7wihs.fsf@earth.catern.com> <83shuzt8iz.fsf@gnu.org> <87y44rudzi.fsf@earth.catern.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1469383165 27646 80.91.229.3 (24 Jul 2016 17:59:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 24 Jul 2016 17:59:25 +0000 (UTC) Cc: emacs-devel@gnu.org To: sbaugh@catern.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 24 19:59:19 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bRNgI-0003RR-Bs for ged-emacs-devel@m.gmane.org; Sun, 24 Jul 2016 19:59:14 +0200 Original-Received: from localhost ([::1]:56951 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bRNgH-0006YY-Gd for ged-emacs-devel@m.gmane.org; Sun, 24 Jul 2016 13:59:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49015) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bRNfm-0006YG-QA for emacs-devel@gnu.org; Sun, 24 Jul 2016 13:58:43 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bRNfi-0005Rn-Nd for emacs-devel@gnu.org; Sun, 24 Jul 2016 13:58:41 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39900) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bRNfi-0005Rj-KA; Sun, 24 Jul 2016 13:58:38 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4091 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bRNfh-0002Bt-Gk; Sun, 24 Jul 2016 13:58:38 -0400 In-reply-to: <87y44rudzi.fsf@earth.catern.com> (sbaugh@catern.com) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:206089 Archived-At: > From: sbaugh@catern.com > Date: Sun, 24 Jul 2016 13:45:21 -0400 > > But there are many Elisp functions that use exec-path. For example, > browse-url uses executable-find (which uses exec-path) to determine > which browsers are available. If exec-path (or maybe just all its users > in core) is not tweaked by environment.el, but the process functions > are, these functions like browse-url will behave in a broken way. If the problem is only with executable-find, we could provide a solution for that one alone. Starting with the simplest one: if the specific environment knows in which directory to look for the browsers, it could simply prepend the directory, making the browser file name an absolute one. Or use locate-file, which accepts path as an argument. Or something. Tweaking exec-path will have a much more dramatic and wide effect, so we should try to avoid that, IMO.