Fork me on GitHub
#cider
<
2020-07-21
>
jhacks18:07:03

I’m trying out cider-toggle-trace-var and 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?

borkdude20:07:14

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?

jr0cket20:07:12

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.

bozhidar04:07:44

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.

dpsutton20:07:30

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

dpsutton20:07:53

at work we recently had to have personal ones so put a template in the readme and added it to gitignore

borkdude20:07:25

That's my feeling too. I don't want to dictate how people's editor config should look like.

borkdude20:07:07

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

dpsutton20:07:35

yes. jack in with a prefix allows editing of the jack in command

dpsutton20:07:58

the keybinding is C-c M-j so C-u C-c M-j or C-u m-x cider-jack-in

borkdude20:07:05

cool, thanks

jr0cket20:07:09

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

borkdude20:07:44

Right, and that's a good reason not to include it in source control, because everyone wants to have a slightly different one

jr0cket20:07:45

Reading the docs for Carve, the PR seems unrelated to the use of Carve. So I wouldn't even add this to the docs.

borkdude20:07:08

this is carve, not calva

jr0cket20:07:13

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.

borkdude21:07:09

The PR is intented to make carve unit tests work with CIDER

dominicm20:07:08

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.

dominicm20:07:01

Vim doesn't really have any directory config, and the user space solutions are pretty flexible.

dpsutton20:07:10

what is "edge" here?

jr0cket20:07:29

Juxt Edge, a curated way to write Clojure projects https://www.juxt.land/edge/index.html

borkdude20:07:09

The new browser from Microsoft? Although I suspect that's not what he meant

dpsutton20:07:32

yeah that's the only thing i can think of called edge. maybe is a vim plugin or something

dpsutton21:07:49

never used it. i'll give it a shot next time

dpsutton21:07:27

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

dominicm06:07:43

The edge docs are more useful. It's a repo you clone, and build your application in. The idea is that the "framework" can be modified very easily. So there's never a blocker to going to production. There's a small template which helps you create an application within the repo.