emacs native compiler error
does anyone know what’s wrong with this? I try to download evil for emacs but encounter a native compiler error, and doom-mode-line also has this problem
Error (use-package): evil/:catch: Native compiler error: (lambda (arg0 arg1 &optional arg2) (let ((f #’set-window-buffer)) (funcall f arg0 arg1 arg2))), “Compiling c:/Users/10747/AppData/Roaming/.emacs.d/eln-cache/29.1-ece58e2c/subr–trampoline-7365742d77696e646f772d627566666572_set_window_buffer_0.eln…
this is my evil config in init.el
(use-package evil
:init
(setq evil-want-integration t)
(setq evil-want-keybinding nil)
(setq evil-want-C-u-scroll t)
(setq evil-want-C-i-jump nil)
:config
(evil-mode 1)
; use C-g to go to normal mode
(define-key evil-insert-state-map (kbd "C-g") 'evil-normal-state)
;; Use visual line motions even outside of visual-line-mode buffers
(evil-global-set-key 'motion "j" 'evil-next-visual-line)
(evil-global-set-key 'motion "k" 'evil-previous-visual-line)
(evil-set-initial-state 'messages-buffer-mode 'normal)
(evil-set-initial-state 'dashboard-mode 'normal))
my doom-mode-line config
(use-package doom-modeline
:init (doom-modeline-mode 1)
:custom ((doom-modeline-height 15)))
I try to ask gpt and search for google and change emacs to version 29.2, 29.4, but all have the same problem, and i change emacs to version 27.1, this time the plugin counsel
have error “error (use-package): counsel/:catch: symbol’s function definition is void: defvar-1” , this is my ivy and counsel config
(use-package ivy
:diminish
:bind (("C-s" . swiper)
:map ivy-minibuffer-map
("TAB" . ivy-alt-done)
("C-l" . ivy-alt-done)
("C-j" . ivy-next-line)
("C-k" . ivy-previous-line)
:map ivy-switch-buffer-map
("C-k" . ivy-previous-line)
("C-l" . ivy-done)
("C-d" . ivy-switch-buffer-kill)
:map ivy-reverse-i-search-map
("C-k" . ivy-previous-line)
("C-d" . ivy-reverse-i-search-kill))
:config
(ivy-mode 1))
(use-package counsel
:config
(counsel-mode 1))
Happytech_web is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.