This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-02
Channels
- # announcements (1)
- # architecture (1)
- # aws (21)
- # babashka (37)
- # beginners (173)
- # boot (12)
- # chlorine-clover (5)
- # cider (36)
- # clara (11)
- # clj-kondo (25)
- # clojure (128)
- # clojure-europe (7)
- # clojure-finland (3)
- # clojure-germany (2)
- # clojure-nl (57)
- # clojure-uk (23)
- # clojurescript (71)
- # clojurex (1)
- # core-async (30)
- # core-typed (5)
- # cursive (35)
- # datomic (8)
- # duct (4)
- # emacs (8)
- # exercism (41)
- # fulcro (116)
- # jackdaw (4)
- # jobs-discuss (6)
- # juxt (4)
- # kaocha (16)
- # leiningen (14)
- # malli (5)
- # observability (4)
- # off-topic (2)
- # pathom (19)
- # pedestal (29)
- # re-frame (64)
- # reitit (18)
- # ring (8)
- # shadow-cljs (3)
- # sql (13)
- # tools-deps (32)
- # tree-sitter (5)
- # yada (17)
Using it daily!
Is anyone using abo-abo/lispy? I am trying to eval the entire namespace (like cider C-c C-k
but I can’t find if that is possible. Currently I have to eval e
each form individually first to be able to eval something in the middle of the file
I use lispy but just use the regular cider eval commands in tandem with it
@g3o cider-eval-buffer
evaluates the whole namespace on the current buffer.
i loved lispy but when i tried it some time back i found some parts to be too rough so sadly stopped using it. may be those things (which i don't remember 😅 ) work better now though.
I love lispy
as well, the main wart that shows up for me if I remember is occasionally the lispy-clojure-complete-at-point
function or whatever gets bugged, and symbols like Syntax
get stored somewhere they shouldn't, and company
gets messed up. I tracked down part of the bug at one point but I forget where the wires get crossed, regardless for now I just remove lispy-clojure-complete-at-point
from complete-at-point-functions
altogether when lispy
starts. But yes, that's the general feel I've gotten as well, at times things sort of break, and there are some sharp edges
yeah i agree that some of the tools it provides (such as lispy-eval) are probably beyond the scope of what the project should be and are best ignored in favor of tools like cider and cljr-refactor
i set up a spacemacs layer a few weeks ago and just pave over a keybinding whenever it causes me an issue