After I uncomment prelude-helm-everywhere, start Emacs in daemon mode, and enter emacsclient -t on the terminal, Emacs Prelude starts.
Actual behavior
Entering emacsclient -t just leads to an empty shell prompt, without persistent output on the terminal. Doing emacsclient -t 2> tmp-1, I see the following error in the file: *ERROR*: ‘which-key-mode’ can’t be used with ‘helm-descbinds-mode’.
This is fixed by commenting out in .emacs.d/core/prelude-ui.el
Expected behavior
After I uncomment prelude-helm-everywhere, start Emacs in daemon mode, and enter
emacsclient -t
on the terminal, Emacs Prelude starts.Actual behavior
Entering
emacsclient -t
just leads to an empty shell prompt, without persistent output on the terminal. Doingemacsclient -t 2> tmp-1
, I see the following error in the file:*ERROR*: ‘which-key-mode’ can’t be used with ‘helm-descbinds-mode’
.This is fixed by commenting out in
.emacs.d/core/prelude-ui.el
and then
killall emacs
. After then restarting emacs in daemon mode I can open a client on the terminal as expected.Note that starting emacs without daemon mode with
emacs
works without any issue for me, in any case.There seem to have been changes related to the error in helm-descbinds four months ago. The issue first occurred for me after I updated Prelude today, which I don't do that often.
Steps to reproduce the problem
.emacs.d
curl -L https://git.io/epre | sh
(require 'prelude-helm-everywhere)
in.emacs.d/personal/prelude-modules.el
/usr/bin/emacs --daemon
emacsclient -t
Environment & Version information
Emacs version
GNU Emacs 29.3 (build 1, x86_64-pc-linux-gnu)
Operating system
Arch Linux