unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jake <jforst.mailman@gmail.com>
To: help-guix@gnu.org
Subject: Re: emacs-vertico not working with emacs-next outside of a container
Date: Sun, 29 Sep 2024 06:02:33 +0000	[thread overview]
Message-ID: <CAJqVjv8kbMtmqp1nkhhfroBDOPZdNTnAyaqJcYw4F6iTvttFuQ@mail.gmail.com> (raw)
In-Reply-To: <CAJqVjv_wMeA4wLFpKy+DT75XNjHLNpAcUeY30Me5HydSGX1VLw@mail.gmail.com>

This error was reported upstream
https://github.com/minad/vertico/discussions/501

A solution posted in that thread worked for me:
Delete the eln-cache directory in the user-emacs-directory

Cheers
Jake

On Sun, Sep 15, 2024 at 12:59 PM Jake <jforst.mailman@gmail.com> wrote:

> Hello
>
> I'm getting an error with "emacs-vertico" when using "emacs-next", but it
> only occurs when the packages are installed in the default user profile or
> in an ordinary shell; it doesn't occur in a container. It also doesn't
> occur with "emacs" (29.4).
>
> guix shell emacs-next emacs-vertico -- emacs -Q --eval "(progn (require
> 'vertico) (vertico-mode 1) (call-interactively 'execute-extended-command))"
> gives the error:
> Error in post-command-hook (vertico--exhibit): (void-function
> compat--completion-metadata-get)
>
> the same error does not happen in a container:
> guix shell --container --network --preserve='^DISPLAY$'
> --preserve='^XAUTHORITY$' --preserve='^LANG$' --expose=$XAUTHORITY --no-cwd
> emacs-next emacs-vertico -- emacs --eval "(progn (require 'vertico)
> (vertico-mode 1) (call-interactively 'execute-extended-command))"
>
> guix 258aab2
>
> Any ideas?
>
> Thanks
> Jake
>

      reply	other threads:[~2024-09-29  6:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-15 12:59 emacs-vertico not working with emacs-next outside of a container Jake
2024-09-29  6:02 ` Jake [this message]

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJqVjv8kbMtmqp1nkhhfroBDOPZdNTnAyaqJcYw4F6iTvttFuQ@mail.gmail.com \
    --to=jforst.mailman@gmail.com \
    --cc=help-guix@gnu.org \
    /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).