Re: org 9.2.6 and org 9.1.9

> [[https://lists.defectivebydesign.org/archive/html/emacs-orgmode/2012-09/msg01365.html][Installing > Org through the new http://orgmode.org ELPA]] > > - > [[https://lists.defectivebydesign.org/archive/html/emacs-orgmode/2015-08/msg00316.html][latest > org from Elpa error: Invalid function:

Re: org 9.2.6 and org 9.1.9

>> But I don't think the issue is with package.el per se. > Maybe it needs fixes elsewhere as well, but it's via package.el that the > problem is usually exposed. Yes, but I think that is mainly because that is the most common way people install it. The manual is fairly clear on this - don't

RE: org 9.2.6 and org 9.1.9

Hi Stefan, I don’t think I’ve ever seen a root-cause analysis, but I’ve seen many problems that are resolved by some version of a “clean build” of org. Here are some: - [[https://lists.defectivebydesign.org/archive/html/emacs-orgmode/2012-09/msg01365.html][Installing Org through the new

Re: org 9.2.6 and org 9.1.9

> From: Stefan Kangas > Date: Wed, 27 Nov 2019 07:29:24 +0100 > Cc: Jean-Christophe Helary , > Org-mode , Emacs developers > > I disagree with removing Org-mode from Emacs core, as I've explained > elsewhere. I agree. It would go against our previous decisions to have Org in core, for

Re: org 9.2.6 and org 9.1.9

> Here's what I do, at the shell: > > > > emacs -Q -batch -eval "(progn (require 'package) (add-to-list > 'package-archives '(\"org\" . > \"http://orgmode.org/elpa/\;;)) > (package-initialize) (package-refresh-contents) (package-install >

Re: org 9.2.6 and org 9.1.9

> But I don't think the issue is with package.el per se. Maybe it needs fixes elsewhere as well, but it's via package.el that the problem is usually exposed. > You get the same problem if you try to install org-mode manually > without package.el. Depends how you do it. > What is really needed

Re: org 9.2.6 and org 9.1.9

Tim Cross writes: > What is really needed to fix this problem is some mechanism which > will ensure all org related definitions are somehow purged from the > running instance before attempting to install and compile a new > version. That could be one way of going about it. Other solutions have

Re: org 9.2.6 and org 9.1.9

On Wednesday, 27 Nov 2019 at 17:00, Tim Cross wrote: > I would agree that org should be a package in elpa and not bundled into > emacs core. I would argue the opposite! I would like to see org tightly integrated into Emacs, in the same way that gnus now is. Development of org would be in step

Re: org 9.2.6 and org 9.1.9

Jean-Christophe Helary writes: > > Yes, it is a bit of dependency hell. > > I see 2 solutions here: > > 1) org is only provided as a built-in package and updated there when necessary Even if we removed it from GNU ELPA, nothing stops unofficial packages from cropping up when users want to run

Re: org 9.2.6 and org 9.1.9

ersions of a given package installed. Only one of the > can be activated at any given time, because Emacs Lisp doesn't provide any > way to do better, but having both Org-9.1.9 and Org-9.2.6 installed > should be a perfectly normal situation. > > Any misbehavior that results from this should

Re: org 9.2.6 and org 9.1.9

Tim Cross writes: > I would agree that org should be a package in elpa and not bundled into emacs > core. The user can then choose which version to install (ignoring the package > dependency problem). I disagree with removing Org-mode from Emacs core, as I've explained elsewhere. > This

Re: org 9.2.6 and org 9.1.9

But I don't think the issue is with package.el per se. You get the same problem if you try to install org-mode manually without package.el. What is really needed to fix this problem is some mechanism which will ensure all org related definitions are somehow purged from the running instance before

Re: org 9.2.6 and org 9.1.9

t; by emacs. > > > > I think 2 is the right option. package.el was designed such that you > > can have various versions of a given package installed. Only one of the > > can be activated at any given time, because Emacs Lisp doesn't provide > any > > way to do

Re: org 9.2.6 and org 9.1.9

emacs. > > I think 2 is the right option. package.el was designed such that you > can have various versions of a given package installed. Only one of the > can be activated at any given time, because Emacs Lisp doesn't provide any > way to do better, but having both Org-9.1.9 and O

Re: org 9.2.6 and org 9.1.9

cause Emacs Lisp doesn't provide any way to do better, but having both Org-9.1.9 and Org-9.2.6 installed should be a perfectly normal situation. Any misbehavior that results from this should be reported as a bug (especially if it can be reproduced). Stefan

Re: org 9.2.6 and org 9.1.9

, > > Malcolm > > > > From: Emacs-orgmode On Behalf > Of Tim Cross > Sent: Tuesday, November 26, 2019 3:41 PM > To: Nick Dokos > Cc: Org-mode ; Emacs developers > Subject: Re: org 9.2.6 and org 9.1.9 > > CAUTION: This email was received from an

RE: org 9.2.6 and org 9.1.9

ll 'org-plus-contrib))" HTH, Malcolm From: Emacs-orgmode On Behalf Of Tim Cross Sent: Tuesday, November 26, 2019 3:41 PM To: Nick Dokos Cc: Org-mode ; Emacs developers Subject: Re: org 9.2.6 and org 9.1.9 CAUTION: This email was received from an External Source There is a very imp

Re: org 9.2.6 and org 9.1.9

Nick, thank you for your reply. > On Nov 27, 2019, at 4:15, Nick Dokos wrote: > > 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?

Re: org 9.2.6 and org 9.1.9

There is a very important rule which must be followed wrt org-mode installation. It is critical that no version of org is already loaded before installing a new version. This can be quite tricky as many of us have org setups which automatically load some org functionality without explicitly

Re: org 9.2.6 and org 9.1.9

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

org 9.2.6 and org 9.1.9

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. 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