Cannot open load file: No such file or directory, evil-multiedit (DoomEmacs)
davidhaley opened this issue · 2 comments
What did you expect to happen?
Hello,
I enabled multiple-cursors
by uncommenting the line in init.el
, and then ran doom sync
. I restarted the client (and the server). doom doctor
succeeds.
When I use <M-d>
(or <C-x> evil-multiedit-match-and-next
), I expect that it should highlight the word and extend a second cursor to the next occurrence.
What actually happened?
Cannot open load file: No such file or directory, evil-multiedit
Describe your attempts to resolve the issue
I enabled multiple-cursors
by uncommenting the line in init.el
, and then ran doom sync
. I restarted the client (and the server). doom doctor
succeeds.
Steps to reproduce
- Uncomment
multiple-cursors
doom sync
(succeeds)
doom doctor
(succeeds)
<M-d>
(or<C-x> evil-multiedit-match-and-next
)
Package commit
e96624926d724aff98e862221422cd7124a99c19
System Information
generated Feb 03, 2023 22:44:43
system "EndeavourOS Linux" Linux 6.1.9-hardened1-1-hardened x86_64 x
emacs 28.2 ~/.emacs.d/
doom 3.0.0-pre PROFILE=_@0 grafted, HEAD -> master, origin/master, origin/HEAD
e966249 2023-01-01 21:55:13 -0500 ~/.doom.d/
shell /bin/bash
features ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ JPEG
JSON LCMS2 LIBOTF LIBSYSTEMD LIBXML2 M17N_FLT MODULES NATIVE_COMP NOTIFY
INOTIFY PDUMPER PNG RSVG SECCOMP SOUND THREADS TIFF TOOLKIT_SCROLL_BARS X11
XDBE XIM XPM GTK3 ZLIB
traits gui daemon server-running envvar-file custom-file
custom custom-safe-themes
modules :config use-package :completion company vertico :ui doom doom-dashboard
doom-quit hl-todo modeline ophints (popup +defaults) (vc-gutter +pretty)
vi-tilde-fringe workspaces :editor (evil +everywhere) file-templates fold
snippets :emacs dired electric undo vc :checkers syntax :tools (eval
+overlay) lookup lsp magit :lang emacs-lisp json javascript markdown org sh
(web +html +css +lsp) :config (default +bindings +smartparens)
It's working on my Ubuntu machine, but not on my EndeavourOS (arch) machine.
I tried again today and it's working (although I'm not entirely sure why). Closing this issue :)