This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-06
Channels
- # adventofcode (10)
- # ai (2)
- # aleph (2)
- # announcements (21)
- # beginners (25)
- # calva (7)
- # cider (19)
- # clj-kondo (28)
- # clj-on-windows (3)
- # cljdoc (6)
- # clojure (80)
- # clojure-dev (15)
- # clojure-europe (29)
- # clojure-italy (3)
- # clojure-nl (37)
- # clojure-uk (4)
- # clojurescript (3)
- # cloverage (1)
- # conjure (6)
- # core-async (2)
- # cursive (17)
- # datalevin (9)
- # datomic (7)
- # deps-new (23)
- # emacs (4)
- # figwheel-main (6)
- # fulcro (6)
- # honeysql (19)
- # improve-getting-started (4)
- # inf-clojure (2)
- # introduce-yourself (5)
- # jobs (1)
- # leiningen (6)
- # lsp (73)
- # malli (1)
- # nrepl (2)
- # off-topic (37)
- # polylith (9)
- # quil (2)
- # reitit (16)
- # releases (2)
- # remote-jobs (6)
- # rewrite-clj (38)
- # shadow-cljs (1)
- # tools-build (1)
Using Prelude Emacs with Helm Everywhere enabled, & sometimes Swyper seems to get "stuck" with its find pane opened in a bug state. Anyone seen this before (& fixed it?) I figure I could disable Swyper but I do like the search improvements it brings
Swiper would work well with Ivy. I believe that Ivy was originally an extension of swiper. If you're set on Helm, maybe try the ctrl-f package?
Fwiw, bbatsov switched to consult and selectrum in his own personal configuration. Not sure why prelude still uses helm. Most folks have had a positive experience with vertico and selectrum. https://github.com/bbatsov/emacs.d
I swapped over to Helm after trying out Ivy for a bit; considered Vertico/Selectrum but didn't want to swap off Helm due to both familiarity & the high value of integrations. I suspect that Swyper wasn't intended to be part of my Helm workflow; might be a remnant that I should manually fix from when I had Prelude-Ivy enabled. I do like it though, so I'll probably try to fix it before abandoning it. (I might eventually figure out how to intentionally trigger the bugged mode :thinking_face:)