From: Tassilo Horn <tsdh@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [partially solved]
Date: Mon, 26 Apr 2021 16:28:01 +0200 [thread overview]
Message-ID: <87tuntt8f0.fsf@gnu.org> (raw)
In-Reply-To: <jwv1raxrvuj.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> ,----
>>> | Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
>>> | Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
>>> | Error loading autoloads: (wrong-number-of-arguments (3 . 4) 2)
>>> | Unable to activate package ‘texfrag’.
>>> | Required package ‘auctex-11.90.2’ is unavailable
>>> | Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
>>> | Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2)
>>> | Error loading autoloads: (wrong-number-of-arguments (3 . 4) 2)
>>> | Unable to activate package ‘bibretrieve’.
>>> | Required package ‘auctex-11.87’ is unavailable
>>> | Unable to activate package ‘auctex-latexmk’.
>>> | Required package ‘auctex-11.87’ is unavailable
>>> |
>>> `----
>
> Any chance you're running a somewhat old AUCTeX version?
When looking at bibretrieve at MELPA
https://melpa.org/#/bibretrieve
it depends on auctex-11.87 which is from around 2014. Same for the
auctex-latexmk package from
https://melpa.org/#/auctex-latexmk
The texfrag package at MELPA
https://melpa.org/#/texfrag
depends on auctex-11.90.2. So I guess the auctex versions popping up
there are the minimal versions required by some package.
I know we've had some `make-obsolete' calls where the WHEN argument was
missing which produced a `wrong-number-of-arguments' error in at least
the current emacs master but those are all fixed in auctex 13.0.x (not
sure which x but definitely for x in {8,9}).
Maybe the errors come from something different. AUCTeX 13 has some
incompatible changes because we've migrated it to `lexical-binding',
possibly including signature changes where there is now a different
arity.
Bye,
Tassilo
next prev parent reply other threads:[~2021-04-26 14:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 19:51 Ubuntu 16.04 compiled GNU master, today, various problems, macro-expansion and (void-variable nonascii-insert-offset) Uwe Brauer
2021-04-26 12:05 ` [partially solved] (was: Ubuntu 16.04 compiled GNU master, today, various problems, macro-expansion and (void-variable nonascii-insert-offset)) Uwe Brauer
2021-04-26 12:24 ` Eli Zaretskii
2021-04-26 13:58 ` [partially solved] Stefan Monnier
2021-04-26 14:28 ` Tassilo Horn [this message]
2021-04-26 15:31 ` Stefan Monnier
2021-04-26 20:44 ` Uwe Brauer
2021-04-27 5:33 ` Tassilo Horn
2021-04-27 6:32 ` Uwe Brauer
2021-04-27 7:00 ` Tassilo Horn
2021-04-27 6:43 ` Uwe Brauer
2021-04-27 6:21 ` [Some tests] (was: [partially solved]) Uwe Brauer
2021-04-26 20:41 ` [partially solved] Uwe Brauer
2021-04-27 6:53 ` [shadchen and lsp-mode] (was: [partially solved]) Uwe Brauer
2021-04-27 13:25 ` Ubuntu 16.04 compiled GNU master, today, various problems, macro-expansion and (void-variable nonascii-insert-offset) Stefan Monnier
2021-04-27 20:47 ` Uwe Brauer
2021-04-27 20:50 ` Uwe Brauer
2021-04-27 22:29 ` Stefan Monnier
2021-04-28 13:37 ` Uwe Brauer
2021-05-03 1:49 ` Stefan Monnier
2021-05-03 1:51 ` Stefan Monnier
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tuntt8f0.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.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).