Re: "transient-define-suffix" autoload error ?

[David Masterson <dsmasterson@gmail.com>]

David Masterson <dsmasterson@gmail.com> writes:

> Stefan Monnier via Users list for the GNU Emacs text editor
> <help-gnu-emacs@gnu.org> writes:
>
>>> Error loading autoloads: (void-function transient-define-suffix)
>>
>> This error indicates "the" file was miscompiled because it uses
>> `transient-define-suffix` without making sure that macro is actually
>> defined (i.e. without `require`ing `transient`).
>>
>> How to fix it depends on what "the" file is, and why
>> `transient-define-suffix` is there.
>
> That is my problem!  How do you find the file that is causing the error?
> Based on where the error occurs in *Messages* and that it also prints to
> standard error(?) as Emacs is starting, I would guess that the error is
> occuring site-lisp or site-start.  A "--debug-init" doesn't give me
> anything because Emacs hasn't gotten to the init file yet (CMIIAW).
> Therefore, I guess it is not in any of my ,emacs.d/elpa packages.
>
> I recognize what the problem is -- I'm just not sure how to find where
> it is happening.

Followup:

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.

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.
I'm not sure how native compilation works internally, so I have some
questions:

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?

-- 
David Masterson