From: David Masterson <dsmasterson@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Stefan Monnier via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: "transient-define-suffix" autoload error ?
Date: Tue, 18 Jun 2024 16:51:15 -0700 [thread overview]
Message-ID: <LV8P223MB092054FAC17C14E4BEE380F6A2CE2@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <jwvo77x9771.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 18 Jun 2024 19:16:50 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> A '--no-init-file' does make the error go away. That suggests that it is
>> a problem with my packages. The only packages that I am using that use
>> transient (AFAICT) is forge and magit. Debugging them is going to be
>> difficult -- they looked good on requires in my first look.
>
> Ah, then if `--debug-init` does not help, maybe you should
>
> emacs -Q --eval '(setq debug-on-error t debug-on-signal t) \
> -l ~/.emacs.d/init.el
I'm old school -- ~/.emacs -- but I get the idea. ;-)
> which may give you a more interesting backtrace (but beware:
> `debug-on-signal` will also give you false positives about errors which
> aren't ones).
With debug-on-signal, I get:
Debugger entered--Lisp error: (void-variable kmacro-call-mouse-event)
Without debug-on-signal, I get:
Debugger entered--Lisp error: (file-missing "Cannot open load file"
"No such file or directory" "use-package")
require(use-package)
>> I use-package to load almost all of my interesting package, so I tried
>> to ':disabled' these two as a first test. The error still comes up.
>
> Maybe the problem is in `~/.emacs.d/package-quickstart.el(c)`?
I don't have that file.
>> 1. When are the native packages loaded in the startup sequence?
>> 2. Does disabling a package via use-package prevent the native code from
>> loading as well?
>> 3. Is there a way to tell Emacs 28.2 to ignore the native code?
>> 4. Does the natve compiler clean up old code from the cache?
>> 5. Could my error be happening in the native code?
>
> I don't see any indication in what you sent that the problem is linked
> to native compilation. Of course, maybe it is, but my crystal ball is
> screaming "look elsewhere".
Your crystal ball is much more advanced than mine when it comes to
Emacs, so I accept that. However, I think my questions above should be
answered in the Emacs manuals somewhere to not make native compilation
opaque.
I don't trust ":disabled" in use-package. I'm going to try commenting
out forge and magit. I might also try safely removing them from
~/.emacs.d.
--
David Masterson
next prev parent reply other threads:[~2024-06-18 23:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 5:21 "transient-define-suffix" autoload error ? David Masterson
2024-06-18 5:47 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-06-18 21:48 ` David Masterson
2024-06-18 22:27 ` Stefan Monnier
2024-06-18 23:01 ` David Masterson
2024-06-18 23:16 ` Stefan Monnier
2024-06-18 23:51 ` David Masterson [this message]
2024-06-19 2:07 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-06-19 21:24 ` David Masterson
2024-06-19 21:36 ` Stefan Monnier
2024-06-20 5:14 ` Eli Zaretskii
2024-06-19 2:17 ` David Masterson
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=LV8P223MB092054FAC17C14E4BEE380F6A2CE2@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM \
--to=dsmasterson@gmail.com \
--cc=help-gnu-emacs@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.
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).