From: Tim Cross <theophilusx@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Greg Minshall <minshall@umich.edu>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] Re: Fwd: errors when using org-agenda
Date: Sun, 24 Oct 2021 17:59:42 +1100 [thread overview]
Message-ID: <m25ytmzyoy.fsf@blind-drunk.fritz.box> (raw)
In-Reply-To: <87lf2jdn00.fsf@localhost>
Ihor Radchenko <yantar92@gmail.com> writes:
> Tim Cross <theophilusx@gmail.com> writes:
>
>> What would really be needed is some way to check when org is going to be
>> compiled that no existing org functionality is loaded. Doubt this can be
>> easily done within org itself because of a chicken and egg problem - you
>> would have to load org to run the code to check if org is loaded.
>
> I attached a tentative patch checking if org is loaded. It is not
> ideal, but it can capture some scenarios.
>
> The patch will not work if older org.el is loaded before newer version
> of Org. Though we may put extra checks in other lisp files.
>
> WDYT?
>
>
This is along the lines of what I was thinking. Of course, the big
limitation is requirement org.el is not loaded. I would imagine it is
rare for org to be loaded and org.el not to be? However, I think this
sort of approach i.e. warning if there is an attempt to upgrade org when
org is already loaded, is the way to go. Achieving this in a clean and
reliable manner is the challenge. False positives are an issue as that
would likely prevent legitimate upgrades.
next prev parent reply other threads:[~2021-10-24 7:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 20:35 errors when using org-agenda William McCoy
2021-10-23 0:46 ` Fwd: " William McCoy
2021-10-23 1:57 ` Tim Cross
2021-10-23 10:26 ` Greg Minshall
2021-10-23 11:34 ` Tim Cross
2021-10-23 18:07 ` Greg Minshall
2021-10-23 18:21 ` Tim Cross
2021-10-24 0:45 ` Thomas S. Dye
2021-10-24 5:05 ` Greg Minshall
2021-10-24 6:44 ` Tim Cross
2021-10-24 10:55 ` Greg Minshall
2021-10-24 5:12 ` [PATCH] " Ihor Radchenko
2021-10-24 6:59 ` Tim Cross [this message]
2021-10-24 8:16 ` Max Nikulin
2021-10-24 8:34 ` Ihor Radchenko
2021-10-27 16:46 ` Max Nikulin
2022-09-11 9:22 ` Ihor Radchenko
2021-10-23 14:49 ` William McCoy
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=m25ytmzyoy.fsf@blind-drunk.fritz.box \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=minshall@umich.edu \
--cc=yantar92@gmail.com \
/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).