GNU bug report logs - #64834
28.2; Auctex fails to load properly

Previous Next

Full log

Message #14 received at 64834 <at> debbugs.gnu.org (full text, mbox):

From: Roger Lipsett <roger.lipsett <at> gmail.com>
To: Tassilo Horn <tsdh <at> gnu.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 64834 <at> debbugs.gnu.org
Subject: Re: bug#64834: 28.2; Auctex fails to load properly
Date: Mon, 24 Jul 2023 13:20:45 -0400

[Message part 1 (text/plain, inline)]

I did copy the elpa subdirectory originally. I just nuked it and
reinstalled auctex from the package list screen, and received many messages
of the form


Compiling file /Users/rlipsett/.emacs.d/elpa/auctex-13.2.1/auctex.el at Mon
Jul 24 13:15:36 2023
Entering directory ‘/Users/rlipsett/.emacs.d/elpa/auctex-13.2.1/’

Compiling file /Users/rlipsett/.emacs.d/elpa/auctex-13.2.1/bib-cite.el at
Mon Jul 24 13:15:36 2023
bib-cite.el:590:1: Error: Lisp nesting exceeds ‘max-lisp-eval-depth’

Compiling file /Users/rlipsett/.emacs.d/elpa/auctex-13.2.1/context-en.el at
Mon Jul 24 13:15:36 2023
context-en.el:33:1: Error: Lisp nesting exceeds ‘max-lisp-eval-depth’


M-x list-load-path-shadows says "No Emacs Lisp load-path shadowings were
found".

I am quite sure, as I suspect you are, that this is a migration problem.
I'm happy to start over, but I thought I had already done that. My Emacs
28.2 is installed via HomeBrew. What would you suggest I try if I want to
wipe all traces from my system and restart it? (BTW, I do not refer to
ansi-color-faces-vector
in my init file, and actually if I remove my init file (rename it) I still
get the same errors.)

On Mon, Jul 24, 2023 at 12:55 PM Tassilo Horn <tsdh <at> gnu.org> wrote:

> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> Hi Roger and Eli,
>
> >> From: Roger Lipsett <roger.lipsett <at> gmail.com>
> >> Date: Mon, 24 Jul 2023 11:08:24 -0400
> >>
> >> I recently switched from an Intel Mac to an Apple Silicon mac, and
> >> Auctex no longer loads properly.
>
> How did you switch?  Especially, did you copy over ~/.emacs.d/elpa/?
>
> >> If I start an emacs server, set debug-on-error to t, and try to load
> >> a .tex file, I get the following, and the first line below continues
> >> until I get the message "error lisp nesting exceeds
> >> 'max-lisp-eval-depth'".
> >>
> >>   internal--fill-string-single-line("Use the command `TeX-Omega-mode'
> to change this va...")
> >>   internal--fill-string-single-line("Use the command `TeX-Omega-mode'
> to change this va...")
> >>   internal--fill-string-single-line("Use the command `TeX-Omega-mode'
> to change this va...")
> >>   internal--format-docstring-line("Use the command `%s' to change this
> variable." TeX-Omega-mode)
> >>   #f(compiled-function (arg1 arg2 &rest rest) "Define a new minor mode
> MODE.\nThis defines the
>
> I cannot reproduce that.  I've tried emacs 28.2 with auctex 13.2.1 (on
> GNU/Linux) from ELPA with a sample TeX file also declaring TeX-engine:
> omega as a file local property.  The (obsolete) TeX-Omega-mode is
> properly activated.
>
> >> If I also set debug-on-signal and try to byte-compile tex.el, which is
> >> where the previous error seemed to occur, I get the following:
> >>
> >> Debugger entered--Lisp error: (void-variable ansi-color-faces-vector)
> >>   default-toplevel-value(ansi-color-faces-vector)
> >>   custom-initialize-reset(ansi-color-faces-vector (funcall
> #'#f(compiled-function () #<bytecode
> >> 0x1ca1c2cd84e54>)))
>
> That also works fine for me...  Do you also get that error when starting
> a fresh emacs and evaluating (require 'ansi-color) in *scratch* or M-:?
> Actually, ansi-color-faces-vector does exist in emacs 28.2 though it is
> obsolete.  Do you use that variable somewhere in your configuration?  It
> looks a bit like you would use it without requiring ansi-color first...
>
> >> In GNU Emacs 28.2 (build 1, aarch64-apple-darwin21.1.0, NS
> appkit-2113.00 Version 12.0.1 (Build
> >> 21A559))
> >>  of 2023-02-22 built on armbob.lan
> >> Windowing system distributor 'Apple', version 10.3.2299
> >> System Description:  macOS 13.4
>
> It's hard to tell what's wrong here.  I'd start by looking at the output
> of M-x list-load-path-shadows RET to check if there are obsolete elisp
> files on the load-path.  If there aren't, I'd try nuking
> ~/.emacs.d/elpa/ and reinstalling the packages anew so that they are
> byte-compiled again (with emacs 29.1, there's a package-recompile-all
> command making that much easier).
>
> Bye,
> Tassilo
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.