This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (82)
- # beginners (70)
- # boot (34)
- # boot-dev (13)
- # cider (45)
- # clara (4)
- # cljs-dev (3)
- # cljsrn (2)
- # clojure (91)
- # clojure-art (8)
- # clojure-czech (1)
- # clojure-dusseldorf (3)
- # clojure-france (11)
- # clojure-germany (1)
- # clojure-greece (39)
- # clojure-hamburg (1)
- # clojure-italy (24)
- # clojure-norway (2)
- # clojure-spec (7)
- # clojure-uk (31)
- # clojurescript (56)
- # core-async (7)
- # cursive (8)
- # data-science (10)
- # datomic (41)
- # duct (7)
- # emacs (1)
- # events (1)
- # fulcro (83)
- # graphql (6)
- # klipse (1)
- # leiningen (28)
- # lumo (67)
- # off-topic (14)
- # om (9)
- # onyx (3)
- # perun (4)
- # re-frame (22)
- # reagent (11)
- # ring-swagger (2)
- # rum (1)
- # specter (46)
- # sql (13)
- # uncomplicate (17)
- # unrepl (114)
big big appreciation for the simple change in the repl to quickly include the repl utilities. Hitting
, in the repl brings up that handy menu and
require-repl-utils is outstanding!
Someone should do a quick and dirty Cider Emacs/spacemacs video on how they develop with clojure. I’m always worried im missing helpful features because i dont know what i dont have 🙂 Of course, there are probably 10 of them out there i haven’t watched…
It's not a screencast, but several folks are doing precisely that (for CIDER as well as other tools) over on ClojureVerse: https://clojureverse.org/t/share-the-nitty-gritty-details-of-your-clojure-workflow/1208 Lots to learn! 😄
I have a few of them: https://www.youtube.com/channel/UCD_9SmDPrAe-sZAfSB9tjdg Mostly this one: https://www.youtube.com/watch?v=4ecC3jqHooc
@drewverlee @magnars zombie themed game development is exactly that http://www.parens-of-the-dead.com
@bozhidar I just tested the xref.clj code, it works verbatim fwiw. But I don't really see the value given that it works on a symbol not a var for cross-referencing.
@dominicm I’m not saying there’s not room for improvement there. 🙂 Ideally potential matches should be resolved to make sure they are really the var you’re looking for, but that’s relatively easy to do.
#'clojure.core/ns is shadowed in
#'clojure.core/keyword with it's ns parameter.
> It does, although input becomes harder for clients. Isn’t the input always a var? Not sure how it becomes harder for clients.
i'll check it tonight. just wondering if it was me or in general. i think someone did some work on the nrepl side recently, but also i may not have restarted emacs since pulling
#'clojure.core/ns is shadowed in
#'clojure.core/keyword with it’s ns parameter.
Yeah, that’s true, but few things are ideal and I’m happy to settle for something that’s useful. 🙂
To deal properly with locals we need to parse the code and even then, there would be some potential for mistakes.
Because building the AST for the project is ridiculously slow and you have to keep rebuilding it after changes for each file.
Depends on how big the project is. It was slow enough to decide I don’t want anything related to parsing code in CIDER itself.
And I seem to recall there were a ton of bugs related to the parser, at least in the early days.
I’ve always liked the simplicity of relying on just the application state - felt very Lispy to me.
It just occurred to me that I do recall seeing a 2 minute AST on a project in the past. We've not reached that scale on my current project yet though.
The xref code would need some tweaking to integrate the locations where the match was found
And maybe a bit of general cleanup. 😄 I seem to recall it was written in the era of Clojure 1.2 or something like this.