From: Ihor Radchenko <yantar92@posteo.net>
To: Justin <justinvallon@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-element loading fails with "regexp" argument not "stringp"
Date: Wed, 05 Jul 2023 10:35:57 +0000 [thread overview]
Message-ID: <877creabn6.fsf@localhost> (raw)
In-Reply-To: <2ff109c7-b3ec-27ac-e75d-ae5ddac14746@vallon.homeip.net>
Justin <justinvallon@gmail.com> writes:
> Using emacs 26.1 (in case it matters). Loading is failing at:
>
> (defconst org-element--current-element-re
> (rx
> (or
> (group-n 1 (regexp org-element--latex-begin-environment-nogroup))
>
> rx is a macro, and so org-element* is not being evaluated. It's
> complaining that the argument to regexp is not a stringp.
>
> Does the rx argument need a backquote? org-element-clock-line-re uses
> rx-to-string with a backquote?
No, it does not need.
The failure is because Emacs 26 does not yet support (regex variable).
However, you will see many more failures with Emacs 26 on the latest
main.
I am not sure if we need to try tackling them all, considering that Org
9.7 will not need to be compatible with Emacs 26.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-07-05 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 23:51 [BUG] org-element loading fails with "regexp" argument not "stringp" Justin
2023-07-05 10:35 ` Ihor Radchenko [this message]
2023-07-05 16:00 ` [PATCH] Fix Emacs-26 compatibility (was: Re: [BUG] org-element loading fails with "regexp" argument not "stringp") Max Nikulin
2023-07-06 9:54 ` Ihor Radchenko
2023-07-08 4:56 ` [PATCH v2] " Max Nikulin
2023-07-08 9:18 ` 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=877creabn6.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=justinvallon@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).