Re: How to make Emacs use ELPA version of `compat'?

RangHo Lee <[email protected]> writes:

> Hello, everyone.
>
> First time requesting for help in Emacs mailing list.
>
> I am using Vertico (https://github.com/minad/vertico) for
> minibuffer completion. Recently, a new commit that
> requires `compat' version 31 (namely, the `set-local'
> function) was introduced.
>
> Naturally, I opened up the package list menu, marked
> `compat' for update, and performed upgrade procedure just
> like other ELPA packages.  (Note that I already have
> `package-install-upgrade-built-in' set as t.)
>
> However, upon running `restart-emacs', it seems that Emacs
> is loading the built-in version (30.2.9999) even though I
> installed the newer version already.
>
> I've checked the contents of `load-path' and the package
> menu, but both look fine to me. The newer version appears
> before system elisp directory, and the package info page
> says that `compat' is "installed" and "shadowing a
> built-in package".
>
> To enable the newer version, I need to click the correct
> version in the package info page and re-install.
>
> Is there a way to make Emacs always prefer the version
> from ELPA?

What is your evidence that Emacs is loading the built-in
(older) version of ‘compat’ instead of the newer version
that you installed with the package manager?

Try:

   1. emacs -Q
   2. C-h v load-path RET
      Confirm that ‘load-path’ contains only the Emacs
      predefined directories.
   3. M-x package-initialize RET
   4. C-h v load-path RET
      Confirm that ‘load-path’ contains the directories of
      your installed packages before the predefined
      directories
   5. Perform whatever test it is that you are using for
      ‘compat’.  If Emacs is still failing to find the newer
      version of ‘compat’, then report your test(s) and
      results to this mailing list.

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