[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Unable to get current or via use-package
From: |
João Pedro de Amorim Paula |
Subject: |
Re: Unable to get current or via use-package |
Date: |
Thu, 10 Feb 2022 18:01:32 -0300 |
On 10 February 2022 17:57, João Pedro de Amorim Paula
<jpedrodeamorim@gmail.com> wrote:
> I had a similar issue in the recent past and was able to come up with a
> solution using the built-in package.el. Not sure how to make it work
> with use-package, but that at least seems to solve the issue of it not
> installing the ELPA version.
Forgot to add the link to my previous email, oops!
https://lists.gnu.org/archive/html/emacs-orgmode/2022-02/msg00062.html
--
João Pedro de Amorim Paula
IT undergraduate at Universidade Federal do Rio Grande do Norte (UFRN)
- Unable to get current or via use-package, Loris Bennett, 2022/02/09
- Re: Unable to get current or via use-package, Eric S Fraga, 2022/02/09
- Re: Unable to get current or via use-package, Loris Bennett, 2022/02/09
- Re: Unable to get current or via use-package, Greg Minshall, 2022/02/09
- Re: Unable to get current or via use-package, João Pedro de Amorim Paula, 2022/02/10
- Re: Unable to get current or via use-package,
João Pedro de Amorim Paula <=
- Re: Unable to get current or via use-package, Loris Bennett, 2022/02/17
- Re: Unable to get current or via use-package, João Pedro de Amorim Paula, 2022/02/18
- Re: Unable to get current or via use-package, João Pedro de Amorim Paula, 2022/02/18
- Re: Unable to get current or via use-package, Loris Bennett, 2022/02/21
RE: Unable to get current or via use-package, Cook, Malcolm, 2022/02/09
RE: Unable to get current or via use-package, Cook, Malcolm, 2022/02/10