From: Max Nikulin <manikulin@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-orgmode@gnu.org, Eli Zaretskii <eliz@gnu.org>,
59882@debbugs.gnu.org
Subject: Re: bug#59882: Multiple versions of Org in load-path problem
Date: Mon, 26 Dec 2022 19:25:49 +0700 [thread overview]
Message-ID: <3f0ead96-4424-18a9-394f-680fc135d39c@gmail.com> (raw)
In-Reply-To: <877cyeqvh4.fsf@localhost>
On 26/12/2022 18:01, Ihor Radchenko wrote:
> Ihor Radchenko writes:
>> 1. ~/Git/with-emacs.sh/with-emacs.sh -e emacs-27 -O -- -l org
> I was finally able to reproduce using emacs-26.
>
> Maybe your Emacs 27 is older than mine? I have GNU Emacs 27.2
Debian stable and Ubuntu LTS have Emacs-27.1 only, so I am testing
1:27.1+1-3ubuntu5
Following the with-emacs.sh script I have tried
mkdir /tmp/emcs
emacs --quick --eval '(setq user-emacs-directory "/tmp/emcs/")' --eval
'(setq user-init-file "/tmp/emcs/init.el")' -l package --eval '(setq
package-user-dir "/tmp/emcs/elpa/")' --eval '(package-initialize)'
--eval '(package-refresh-contents)' -l org
I had no problem to select Org-9.6 from the buffer generated by
`list-packages'. Compilation errors and the error during next startup
are the same as I reported before.
I found just single commit to lisp/emacs-lisp/package.el between
emacs-27.1 and emacs-27.2:
1fc9de4b81c 2020-10-30 19:20:24 -0700 Glenn Morris: Improve
reproducibility of generated -pkg.el files
So I am still surprised that you can not reproduce the issue.
next prev parent reply other threads:[~2022-12-26 12:27 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 2:50 Multiple versions of Org in load-path problem David Masterson
2022-12-06 5:36 ` tomas
2022-12-06 7:04 ` David Masterson
2022-12-07 13:30 ` Ihor Radchenko
2022-12-08 3:27 ` David Masterson
2022-12-08 7:16 ` David Masterson
2022-12-08 7:26 ` Ihor Radchenko
2022-12-08 18:24 ` David Masterson
2022-12-08 19:31 ` Michel Schinz
2022-12-08 21:56 ` David Masterson
2022-12-08 22:56 ` Tim Cross
2022-12-09 5:00 ` David Masterson
2022-12-09 6:56 ` Tim Cross
2022-12-09 15:49 ` Sharon Kimble
2022-12-10 20:38 ` Tom Gillespie
2022-12-09 7:17 ` bug#59882: " Eli Zaretskii
2022-12-09 7:43 ` David Masterson
2022-12-09 11:57 ` Eli Zaretskii
2022-12-09 19:40 ` Cook, Malcolm
2022-12-09 19:51 ` David Masterson
2022-12-09 20:27 ` Eli Zaretskii
2022-12-10 14:01 ` Ihor Radchenko
2022-12-14 9:51 ` Ihor Radchenko
2022-12-14 12:59 ` Eli Zaretskii
2022-12-14 13:37 ` Ihor Radchenko
2022-12-14 14:35 ` Stefan Monnier
2022-12-14 16:02 ` Max Nikulin
2022-12-15 4:17 ` Stefan Monnier
2022-12-15 4:56 ` Ihor Radchenko
2022-12-16 12:36 ` Max Nikulin
2022-12-16 14:47 ` Ihor Radchenko
2022-12-18 15:24 ` Max Nikulin
2022-12-18 15:40 ` Stefan Monnier
2023-04-06 16:09 ` Max Nikulin
2023-04-06 21:25 ` Stefan Monnier
2023-04-19 4:20 ` Tom Gillespie
2022-12-25 9:48 ` Ihor Radchenko
2022-12-25 11:46 ` Max Nikulin
2022-12-26 8:44 ` Ihor Radchenko
2022-12-26 11:01 ` Ihor Radchenko
2022-12-26 12:25 ` Max Nikulin [this message]
2022-12-27 9:47 ` Ihor Radchenko
2022-12-27 9:56 ` Max Nikulin
2023-02-03 11:02 ` Ihor Radchenko
2023-02-03 12:15 ` Eli Zaretskii
2023-02-03 20:01 ` Tim Cross
2023-02-14 22:53 ` Gregor Zattler
2023-02-16 12:14 ` Max Nikulin
2023-02-21 5:22 ` Richard Stallman
2023-02-21 12:32 ` Eli Zaretskii
2023-02-21 17:26 ` Bhavin Gandhi
2023-02-22 10:48 ` Ihor Radchenko
2023-02-22 16:58 ` Bhavin Gandhi
2023-02-23 9:35 ` Ihor Radchenko
2023-04-06 15:02 ` Max Nikulin
2022-12-14 14:25 ` Stefan Monnier
2022-12-14 21:49 ` Cook, Malcolm
2022-12-09 19:47 ` Cook, Malcolm
2022-12-08 21:50 ` Cook, Malcolm
[not found] ` <87o7se74bf.fsf@penguin>
2022-12-08 7:19 ` David Masterson
2022-12-08 9:10 ` Ihor Radchenko
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=3f0ead96-4424-18a9-394f-680fc135d39c@gmail.com \
--to=manikulin@gmail.com \
--cc=59882@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yantar92@posteo.net \
/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).