From: Loris Bennett <loris.bennett@fu-berlin.de>
To: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Unable to get current or via use-package
Date: Thu, 10 Feb 2022 08:09:08 +0100 [thread overview]
Message-ID: <878rujkxkb.fsf@hornfels.zedat.fu-berlin.de> (raw)
In-Reply-To: <CH0PR20MB394799AC93B9C9F22A55FB27BE2E9@CH0PR20MB3947.namprd20.prod.outlook.com> (Malcolm Cook's message of "Wed, 9 Feb 2022 16:28:23 +0000")
"Cook, Malcolm" <MEC@stowers.org> writes:
>>(use-package org
>>:ensure org-contrib)
>
> I believe `:ensure org-contrib` is no longer needed.
Well, I would need it if I actually wanted anything from org-contrib,
but I really have to check whether this is still the case.
> I tend to use the org-mode from the package manager, but do not do it interactively from within emacs. Instead, which when I want to refresh org, I do from the command line:
>
> emacs -Q -batch -eval "(progn (require 'package) (package-initialize) (package-refresh-contents) (package-install 'org))"
Is that necessary? Can't I just use the package manager to update Org
along with any other packages? Or does the issue about not visiting and
.org file before installing via the package manager apply to updates
too?
> Also, early in my init.el, as extra level of precaution against getting the built-in org-mode, I ensure it never gets loaded:
> (require 'cl-seq) (delete (car (cl-member "lisp/org" load-path :test #'string-match)) load-path)
Interesting, although I would generally want at least some version of
Org even if a more recent version is installed but somehow broken.
>>
>>I moved the old-plus-contrig ELPA folder out the way. However, I now
>>just get the built-in version of Org:
>>
>>Org mode version 9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)
>>
>>Is this a problem use-package has with built-in packages, as described here
>>
>>https://github.com/jwiegley/use-package/issues/319
>>
>>? Or am I doing something wrong? Or do I just need to install via M-x
>>list-packages (bearing in mind the caveat about not visiting an org file
>>beforehand)?
>>
>>Cheers,
>>
>>Loris
>>
>>--
>>This signature is currently under construction.
>>
next prev parent reply other threads:[~2022-02-10 7:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 13:25 Unable to get current or via use-package Loris Bennett
2022-02-09 14:02 ` Eric S Fraga
2022-02-09 15:51 ` Loris Bennett
2022-02-09 17:18 ` Greg Minshall
2022-02-10 20:57 ` João Pedro de Amorim Paula
2022-02-10 21:01 ` João Pedro de Amorim Paula
2022-02-17 15:00 ` Loris Bennett
2022-02-18 21:32 ` João Pedro de Amorim Paula
2022-02-18 21:36 ` João Pedro de Amorim Paula
2022-02-21 6:40 ` Loris Bennett
2022-02-09 16:28 ` Cook, Malcolm
2022-02-10 7:09 ` Loris Bennett [this message]
2022-02-10 8:12 ` Tim Cross
2022-02-10 9:01 ` Ihor Radchenko
2022-02-10 18:39 ` Tim Cross
2022-02-10 15:19 ` Cook, Malcolm
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rujkxkb.fsf@hornfels.zedat.fu-berlin.de \
--to=loris.bennett@fu-berlin.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).