This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-06-03
Channels
- # aws (12)
- # beginners (12)
- # biff (10)
- # calva (1)
- # cider (10)
- # cljfx (1)
- # clojure (2)
- # clojure-conj (1)
- # clojure-europe (25)
- # clojure-madison (1)
- # clojure-nl (1)
- # clojure-norway (12)
- # clojure-sweden (4)
- # clojure-uk (6)
- # datomic (11)
- # dev-tooling (3)
- # emacs (5)
- # gratitude (1)
- # introduce-yourself (7)
- # java (3)
- # jobs (1)
- # london-clojurians (2)
- # lsp (23)
- # off-topic (4)
- # practicalli (9)
- # quil (6)
- # re-frame (3)
- # reagent (4)
- # remote-jobs (1)
- # ring (1)
- # shadow-cljs (18)
- # squint (67)
- # tools-deps (5)
- # xtdb (4)
- # yamlscript (12)
How long does it take your "helm-swoop" to go from issuing the command to seeing the results? mine takes like 3 seconds, which seems like forever.
other helm commands from my emacs setup seem slow to, like just bringing up the command history takes 2-3 seconds.
Switch to Vertico/Consult/Embark stack, it's not that complicated and totally worth it. It's faster, it's predictable, it's easily extendable. It already has tons of extensions.
Shouldn't be so slow. Try the usual M-x profiler-start
, use helm a little bit, then M-x profiler-report
.
Thanks @U0G75ARHC and @U06PNK4HG for suggestions. I'll probably try both and see which yields results for me.. I might combine the vertico/consult/embark switch with trying Doom again.