Jim Porter <jporterb...@gmail.com> writes:
Hi Jim,
> When installing Tramp from GNU ELPA on Emacs 29.1, I get a bunch of
> errors (see the attached "tramp-compile.log"). In addition, when I
> start Emacs up the next time, I get this error in the *Messages*
> buffer:
>
> Error loading autoloads: (void-function tramp--with-startup)
>
> If I eval "(require 'tramp)", I get this error:
>
> Debugger entered--Lisp error: (void-function
> tramp-register-crypt-file-name-handler)
> tramp-register-crypt-file-name-handler()
> tramp-register-file-name-handlers()
> #f(compiled-function () #<bytecode 0x1980050a6a75>)()
> run-hooks(tramp--startup-hook)
>
> byte-code("\301\302\303\304#\210\305\306!\210\307\300!\210\310\211\20\207"
> [tramp--startup-hook put tramp-unload-tramp tramp-autoload t provide
> tramp run-hooks nil] 5)
> require(tramp)
> eval-expression((require 'tramp) nil nil 127)
> funcall-interactively(eval-expression (require 'tramp) nil nil 127)
> command-execute(eval-expression)
>
> I'm guessing this is due to Emacs 29.1 having a new method for
> generating autoloads (loaddefs-gen.el). It looks like the Makefile for
> Tramp from ELPA still tries to use the old way of generating
> autoloads, but I guess package.el tries to use the new one, causing
> some kind of conflict. Looking at the generated tramp-autoloads.el, it
> seems to be a lot different from how it was generated in Emacs 28.2,
> and in particular, has some calls to 'tramp--with-startup' (I've
> attached this as well). I don't quite understand what's going on
> beyond that, though...
Yep, it seems to be an autoload problem. An I also don't understand
what's up :-(
I'll try next days to fix it. Achhhhh ...
