From: Jean-Christophe Helary <email@example.com>
To: firstname.lastname@example.org, Emacs developers <email@example.com>
Subject: Re: org 9.2.6 and org 9.1.9
Date: Wed, 27 Nov 2019 08:14:20 +0900 [thread overview]
Message-ID: <68782497-408D-4E97-8CA0-72B41882FB13@traduction-libre.org> (raw)
Nick, thank you for your reply.
> On Nov 27, 2019, at 4:15, Nick Dokos <firstname.lastname@example.org> wrote:
> Jean-Christophe Helary <email@example.com> 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?
At one point I was unable to archive subtrees because some function was undefined.
I uninstalled 9.2.6 and the issues was fixed.
> I have the built-in 9.1.9 org that
> comes with emacs but I run (close to) latest master and I see no
Obviously you are not the typical user... :)
What should happen is that
1) packages.el should see that I'm trying to install a package that requires 9.2.6 as a dependency and it should notify me that 9.1.9 is already installed and do I really want to do that, etc.
2) *or* just consider that it's better for me to use 9.2.6 instead of whatever comes with emacs and make sure that the older package is forgotten by emacs.
But honestly, I think 1) should be the default for any package.
next prev parent reply other threads:[~2019-11-26 23:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-24 13:37 Jean-Christophe Helary
2019-11-26 19:15 ` Nick Dokos
2019-11-26 21:41 ` Tim Cross
2019-11-27 2:59 ` Cook, Malcolm
2019-11-27 3:13 ` Jean-Christophe Helary
2019-11-27 6:18 ` Stefan Kangas
2019-11-27 13:23 ` Stefan Monnier
2019-11-27 17:20 ` Cook, Malcolm
2019-11-27 21:51 ` Tim Cross
2019-11-27 22:01 ` Stefan Monnier
2019-11-26 23:14 ` Jean-Christophe Helary [this message]
2019-11-27 3:24 ` Stefan Monnier
2019-11-27 5:43 ` Jean-Christophe Helary
2019-11-27 6:00 ` Tim Cross
2019-11-27 6:29 ` Stefan Kangas
2019-11-27 6:42 ` Tim Cross
2019-11-27 10:11 ` Stefan Kangas
2019-11-27 13:21 ` Stefan Monnier
2019-11-27 15:44 ` Eli Zaretskii
2019-11-27 7:04 ` Fraga, Eric
2019-11-27 6:34 ` Stefan Kangas
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).