Closed yubrshen closed 2 years ago
It seems related to company-capf. When the issue occured, there was an error related to company-capf.
I'm seeing the same, seems to start happening after a while and my current solution is to restart emacs...
read-from-minibuffer("Lisp expression: " nil (keymap (menu-bar keymap (minibuf "Minibuf" keymap (previous menu-item "Previous History Item" previous-history-element :help "Put previous minibuffer history element in the min...") (next menu-item "Next History Item" next-history-element :help "Put next minibuffer history element in the minibuf...") (isearch-backward menu-item "Isearch History Backward" isearch-backward :help "Incrementally search minibuffer history backward") (isearch-forward menu-item "Isearch History Forward" isearch-forward :help "Incrementally search minibuffer history forward") (return menu-item "Enter" exit-minibuffer :key-sequence "\15" :help "Terminate input and exit minibuffer") (quit menu-item "Quit" abort-recursive-edit :help "Abort input and exit minibuffer") "Minibuf")) (10 . exit-minibuffer) (13 . exit-minibuffer) (7 . minibuffer-keyboard-quit) (C-tab . file-cache-minibuffer-complete) (9 . self-insert-command) (XF86Back . previous-history-element) (up . previous-line-or-history-element) (prior . previous-history-element) (XF86Forward . next-history-element) (down . next-line-or-history-element) (next . next-history-element) (27 keymap (60 . minibuffer-beginning-of-buffer) (114 . previous-matching-history-element) (115 . next-matching-history-element) (112 . previous-history-element) (110 . next-history-element))) t minibuffer-history)
read-minibuffer("Lisp expression: ")
read(nil)
lispy-clojure-complete-at-point()
completion--capf-wrapper(lispy-clojure-complete-at-point optimist)
run-hook-wrapped(completion--capf-wrapper lispy-clojure-complete-at-point optimist)
company--capf-data-real()
company--capf-data()
company-capf(prefix)
apply(company-capf prefix)
company-call-backend-raw(prefix)
apply(company-call-backend-raw prefix)
company--force-sync(company-call-backend-raw (prefix) company-capf)
company-call-backend(prefix)
company--begin-new()
company--perform()
company-auto-begin()```
Thanks, please test.
Thanks for the quick fix! I'll try it.
I sometimes accidentally run into a situation when in the input mode of evil mode with Clojure mode, When I enter any character, I’m kept prompted at the mini-buffer “Lisp expression:” that I don’t know what to do with it. It seemed that it was when I typed a symbol's name.
I tried to enter some text, or Lisp expression, but I still get the same prompt without any helpful feedback, not able to do anything meaningful, useful.
I’m using emacs/Doom, with a copied customization that I don’t fully know. It has Clojure mode, cider running at the buffer. There might be more running that I don’t know.
The problem might be related to “lispy.clojure”, as I saw an error message of
" Syntax error compiling at (src/yubrshen/eta_variances.clj:1:1). No such var: lispy.clojure/pp"
Furthermore, when I disable the lispy feature in emacs-doom's init.el, then the problem is gone.
Please advise how I deal with the situation, even a work-around is fine.