Re: Report issue concerning melpa package

Charles Millar <[email protected]> writes:

>>>
>>> One other observation- while looking over the buffer file list I noticed
>>> that the slime-cl-indent-test.txt was opened.
>>>

If you look at the beginning of ‘slime-cl-indent-test.txt’,
there is an explanation in the comments about its purpose.

>> 3. If you are using Emacs 30, then you could try:
>>     a. Exit your running Emacs.
>>     b. Rename your Emacs initialization file.
>>     c. Start Emacs.
>>     d. Set the value of ‘package-archives’ to include the
>>        melpa-stable archive:
>
> added yesterday as suggested in 
> https://melpa.org/partials/getting-started.html
>
> (add-to-list 'package-archives '("melpa-stable" . 
> "https://stable.melpa.org/packages/") t)
>

I uninstalled Slime to re-install it and realized that I had
forgotten that this package is available in the ‘nongnu’
archive, too.  So, it is available using the default values
of ‘package-archives’ (without using the melpa or
melpa-stable archives).

>>        M-x customize-option package-archives
>
>
>>     e. Using the package manager, install Slime 2.32.
>>        - C-h P slime RET
>>        - Click on the Install button in the Help window
>> 
>
> Still the same errors
>
>

1. After removing Slime, I started Emacs (version 30.x) using
‘emacs -Q’ and installed it again using:
   - C-h P slime RET
   - Clicked on the Install button in the Help window

It installed and produced (the as usual long) *Compile-Log*
buffer that contained many (mostly) harmless warning
messages.  (The buffer has 433 lines of warning messages.)
Although, it would be nice if the missing ‘lexical-binding’
directives were all eliminated.

It also generated an *Async-native-compile-log* buffer that
likewise had many warning messages.  There were zero error
messages in either buffer.

2. Here is the section of the Emacs Lisp Reference manual
that describes the "eager macro expansion" error, if you are
curious:

   (info "(elisp) How Programs Do Loading")

3. Unless someone else has some other ideas, here are some
more steps you could try:

  a. Uninstall Slime, start ‘emacs -Q’, install ‘Slime’
using C-h P.
  b. Or, rename your ‘.emacs.d’ directory, then start Emacs,
and then install ‘Slime’ into an empty .emacs.d directory
tree.
  c. Or, start Emacs using ‘emacs --debug-init’ to see if
you can track down the source of the "eager macro expansion"
error.

-- 
The lyf so short, the craft so long to lerne.
- Geoffrey Chaucer, The Parliament of Birds.