From: Maxim Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: citations: rx problems with emacs-26.3
Date: Sun, 8 Aug 2021 20:34:55 +0700 [thread overview]
Message-ID: <seomi1$785$1@ciao.gmane.io> (raw)
In-Reply-To: <87sfzlc850.fsf@nicolasgoaziou.fr>
On 08/08/2021 03:27, Nicolas Goaziou wrote:
> Maxim Nikulin writes:
>>
>> It seems, rx e.g. in emacs-26.3 does not support all features used in
>> oc.el and oc-csl.el. Loading an org file using git master, I get
>> a warning
>>
>>> Eager macro-expansion failure: (error "rx form ‘regexp’ requires args satisfying ‘stringp’")
>>
>>> diff --git a/lisp/oc-basic.el b/lisp/oc-basic.el
>
> Thanks. Could you send the patch again with a proper commit message,
> using git format-patch?
I going to do it. For a while, I have noticed another problem with a lot
of pcase branches in `org-cite-natbib--style-to-command' in and my
experience is not enough to resolve it. On attempt to byte-compile-file
the following error is reported after significant delay (and CPU fan
becomes more noisy)
oc-natbib.el:108:9:Error: Bytecode overflow
I have tried to comment out some conditions
ls -l lisp/oc-natbib.elc
-rw-rw-r-- 1 ubuntu ubuntu 241882 Aug 8 13:23 lisp/oc-natbib.elc
If more branches are commented out
-rw-rw-r-- 1 ubuntu ubuntu 8525 Aug 8 13:20 lisp/oc-natbib.el
Looks like a kind of combinatorics explosion. It seems, if Emacs-25.2
and 26.3 are considered as supported, this function should be rewritten
to avoid issues with byte compilation.
next prev parent reply other threads:[~2021-08-08 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 10:36 citations: rx problems with emacs-26.3 Maxim Nikulin
2021-08-07 20:27 ` Nicolas Goaziou
2021-08-08 13:34 ` Maxim Nikulin [this message]
2021-08-08 14:14 ` Nicolas Goaziou
2021-08-09 17:18 ` Maxim Nikulin
2021-08-11 5:37 ` Axel Kielhorn
2021-08-11 9:33 ` Nicolas Goaziou
2021-08-11 16:24 ` Maxim Nikulin
2021-08-09 17:10 ` Maxim Nikulin
2021-08-11 9:18 ` Nicolas Goaziou
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='seomi1$785$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).