emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: [Bug] org-persist.el: xdg.el is unavailable in emacs-25.2
Date: Wed, 27 Oct 2021 21:55:42 +0800	[thread overview]
Message-ID: <87zgqu6081.fsf@localhost> (raw)
In-Reply-To: <3e432fa9-545d-fce0-759f-9260161255c7@gmail.com>

Max Nikulin <manikulin@gmail.com> writes:

>> In toplevel form:
>> ox-beamer.el:34:1:Error: Cannot open load file: No such file or directory, xdg
>  >
>  > ...
>
> org.el in the main branch still declares
>
>> ;; Package-Requires: ((emacs "25.1"))
>
> but it seems xdg.el used by org-persist.el was added in emacs-26.0.
>
> I do not actually use emacs-25.2, but it happened that I have a test 
> container for Org based on Ubuntu-18.04.
>
> Either org-persist and org-compat should be updated with some 
> compatibility code or required emacs version should be updated once more.

Technically, the current Emacs version is Emacs 27. So, following our
maintenance convention [1], we should support everything down to Emacs
25 (e.g. 27-2). However, Emacs 28 is going to be out soon-ish and the
problem is not on bugfix branch, but only on main. I am not sure if we
need to follow version-2 convention for main as well. Maybe better
require only version-1? Weaker back-compatibility requirement can allow
us to implement more advanced features relying on more recent Emacs
versions.

[1] https://orgmode.org/worg/org-maintenance.html

Also, org-src.el from bugfix may not run on Emacs 25:

In end of data:
org-src.el:1312:1:Warning: the function ‘replace-buffer-contents’ is not known
    to be defined.

Best,
Ihor


      reply	other threads:[~2021-10-27 14:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 12:35 [Bug] org-persist.el: xdg.el is unavailable in emacs-25.2 Max Nikulin
2021-10-27 13:55 ` Ihor Radchenko [this message]

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=87zgqu6081.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@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).