From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: org 9.2.6 and org 9.1.9 Date: Tue, 26 Nov 2019 14:15:26 -0500 Message-ID: <874kyqcuup.fsf@alphaville.usersys.redhat.com> References: <7D2A3D8D-CB71-4B0D-8839-9633BD9F9C4B@traduction-libre.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:33725) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZgJu-0000ll-Gm for emacs-orgmode@gnu.org; Tue, 26 Nov 2019 14:16:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iZgJt-0004A6-Ez for emacs-orgmode@gnu.org; Tue, 26 Nov 2019 14:16:18 -0500 Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:35368 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iZgJq-000480-Hs for emacs-orgmode@gnu.org; Tue, 26 Nov 2019 14:16:15 -0500 Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1iZgJl-000xiD-9m for emacs-orgmode@gnu.org; Tue, 26 Nov 2019 20:16:09 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Cc: emacs-devel@gnu.org Jean-Christophe Helary writes: > org 9.1.9 is a built-in > > but org 9.2.6 comes as a dependency to some packages and having both installed creates conflicts. > What conflicts are you seeing? I have the built-in 9.1.9 org that comes with emacs but I run (close to) latest master and I see no problems: the only thing I do is to set my load-path to point to the right place (and make sure that that setting precedes the /usr/local/share/emacs/27.0.50/lisp/org setting that emacs adds): (add-to-list 'load-path (expand-file-name "~/elisp/org-mode/lisp")) Although that has been enough for me, it's probably safer to delete from load-path all other org entries, thereby making the built-in version invisible to emacs - in my case, I just have the one: (delete "/usr/local/share/emacs/27.0.50/lisp/org" load-path) That way, if you happen to do something like `(require 'old-org-req)' with a requirement that is not satisfied by current org, but is satisfied by the built-in org, you'd get an error, rather than getting a mixed installation. > Why does that happen ? > > Can't 9.2.6 override 9.1.9 ? It's not the first time I have issues > with that situation and that's extremely confusing. What is the best > way to solve that ? > I think the above should be enough (and IME it is), but maybe someone can think of other things that might trip one up. -- Nick "There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." -Martin Fowler