From: Maxim Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: citations: rx problems with emacs-26.3
Date: Tue, 10 Aug 2021 00:18:47 +0700 [thread overview]
Message-ID: <sero1n$11mt$1@ciao.gmane.io> (raw)
In-Reply-To: <87k0kwc9b0.fsf@nicolasgoaziou.fr>
On 08/08/2021 21:14, Nicolas Goaziou wrote:
> Maxim Nikulin writes:
>
>> 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
>
> Fixed. Thank you.
Nice. Perhaps `org-cite-biblatex-export-citation' should be fixed in a
similar way. There is no error yet but compiled file is significantly
blown up:
-rw-rw-r-- 1 ubuntu ubuntu 13383 Aug 9 02:17 lisp/oc-biblatex.el
-rw-rw-r-- 1 ubuntu ubuntu 48906 Aug 9 17:06 lisp/oc-biblatex.elc
There are a couple of issues with "make single" for emacs-25.2:
Compiling single /home/ubuntu/org-mode/lisp/oc-basic.el...
In end of data:
oc-basic.el:772:1:Warning: the function ‘buffer-hash’ is not known to be
defined.
Compiling single /home/ubuntu/org-mode/lisp/oc-biblatex.el...
Compiling single /home/ubuntu/org-mode/lisp/oc-csl.el...
In toplevel form:
oc-csl.el:90:1:Error: Cannot open load file: No such file or directory,
org-cite
Makefile:59: recipe for target 'oc-csl.elc' failed
make[2]: [oc-csl.elc] Error 1 (ignored)
next prev parent reply other threads:[~2021-08-09 17:19 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
2021-08-08 14:14 ` Nicolas Goaziou
2021-08-09 17:18 ` Maxim Nikulin [this message]
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='sero1n$11mt$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).