This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aws (14)
- # babashka (35)
- # beginners (163)
- # boot (2)
- # calva (5)
- # cider (30)
- # clojure (143)
- # clojure-colombia (1)
- # clojure-europe (5)
- # clojure-nl (11)
- # clojure-spec (1)
- # clojure-uk (16)
- # clojurescript (71)
- # community-development (2)
- # conjure (1)
- # cursive (6)
- # datomic (30)
- # duct (4)
- # figwheel-main (11)
- # fulcro (28)
- # graalvm (3)
- # graphql (23)
- # hoplon (36)
- # jackdaw (24)
- # kaocha (16)
- # lambdaisland (1)
- # leiningen (4)
- # luminus (3)
- # meander (4)
- # observability (1)
- # off-topic (10)
- # pathom (5)
- # re-frame (27)
- # reitit (7)
- # remote-jobs (1)
- # sci (17)
- # shadow-cljs (22)
- # spacemacs (14)
- # sql (61)
- # testing (3)
- # tools-deps (27)
- # vim (2)
- # xtdb (18)
- # yada (2)
I’m trying out
cider-toggle-trace-ns. Is there any way to list the vars or namespaces that are being traced. It looks like some vars have the
cider-traced-face applied and some don’t (in Emacs).
Also, is there anyway to disable all tracing without tracking down each var/namespace individually?
This is the reference I’m using: https://docs.cider.mx/cider/0.23/debugging/tracing.html
Is it a good habit to check in
.dir-locals files into source control? E.g. see https://github.com/borkdude/carve/pull/29.
That PR wants to add a
.dir-locals to "teach" CIDER that it should include
:test profile from deps.edn. What are other ways of doing this?
If it's just a common thing like a :test alias to add the test path, then it seems very low value. It's a general alias that can be added to the
.clojure/deps.edn file and it can be used via
C-u cider-jack-in as well as a .dir-locals.
Depends on the nature of the things in the
.dir-locals.el - typically I check it in and include there stuff that are “standard” for the project. People can have a local
.dir-locals2.el on top of this.
its tough. if someone has more things in their dir-locals its better for it to be gitignored so there's no fighting and unstaged differences all the time
at work we recently had to have personal ones so put a template in the readme and added it to gitignore
That's my feeling too. I don't want to dictate how people's editor config should look like.
Does cider have an option to include alias deps when jacking in? I myself start the REPL always from the command line, but I guess a lot of people just use cider-jack-in
If your project docs include guides on using with tools, you could include an example. There are lots of possible options for .dir-locals, e.g https://practicalli.github.io/spacemacs/clojure-projects/project-configuration.html
Right, and that's a good reason not to include it in source control, because everyone wants to have a slightly different one
Reading the docs for Carve, the PR seems unrelated to the use of Carve. So I wouldn't even add this to the docs.
Can't spell anymore... The docs on the repo of the PR doesn't seem to discuss running carve from a Clojure repl environment, just from a command line or CI service.
It's long been a wish of mine that project vs user configuration was distinguished. Edge does the "wrong" thing here, but the user experience is far better because of it. Edge's dir locals sets a few more things though.
Vim doesn't really have any directory config, and the user space solutions are pretty flexible.
Juxt Edge, a curated way to write Clojure projects https://www.juxt.land/edge/index.html
yeah that's the only thing i can think of called edge. maybe is a vim plugin or something
Sorry. JUXT edge. The clojure starter project. https://github.com/juxt/edge This is what is generated: https://github.com/juxt/edge/blob/master/lib/edge-app-template/resources/clj/new/app.template/dir-locals.el
not clear to me though. is that a sample repo that you clone and then change or is it a template for clj-new/lein new