This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-14
Channels
- # aleph (10)
- # announcements (2)
- # beginners (228)
- # calva (18)
- # cider (6)
- # clara (5)
- # cljdoc (25)
- # cljs-dev (22)
- # clojure (78)
- # clojure-dev (30)
- # clojure-europe (2)
- # clojure-finland (1)
- # clojure-italy (32)
- # clojure-nl (21)
- # clojure-uk (126)
- # clojurescript (34)
- # cursive (5)
- # data-science (2)
- # datascript (2)
- # datomic (26)
- # defnpodcast (1)
- # emacs (5)
- # figwheel (5)
- # figwheel-main (3)
- # fulcro (14)
- # graphql (5)
- # jobs (1)
- # keechma (4)
- # nrepl (5)
- # off-topic (35)
- # onyx (3)
- # pedestal (12)
- # random (1)
- # re-frame (35)
- # reagent (8)
- # reitit (20)
- # remote-jobs (5)
- # ring-swagger (20)
- # shadow-cljs (166)
- # sql (43)
- # vim (6)
- # yada (15)
Has anyone seen issues with the which-keys buffer showing up partially behind the minibuffer? I’m using Spacemacs, without too much customization at this point. If I restart Emacs, the problem will go away, but at some point I perform a series of unknown actions and it gets in a bad state (I just haven’t noticed yet what those actions are).
I’m hoping someone has seen this before and would know how it could be fixed without resorting to a restart.
@U08TWB99B maybe it’s related to this https://github.com/syl20bnr/spacemacs/issues/11165 My guess would be an issue with the version of Emacs, especially if you are running Emacs 26 or 27. Or it could be a bug in the which-key package, in which case you could try to pin to an earlier version of which-key package.
An elisp library for monitoring log files during development https://github.com/EwenG/strette.el