Yes, I am loving the rain and my cats are a lot happier too

:thunder_cloud_and_rain:

last night

Of you are still workin on that, this may help... Skip the 'under the covers' section of you want http://jr0cket.co.uk/2019/07/a-deeper-understanding-of-Clojure-CLI-tools.html

There is also a video https://youtu.be/KjCibf3hCOc

> ~/.clojure/deps.edn is created the first time you run the clojure command. I thought that file was laid down by the installer itself (if it doesn't already exist)?

> /usr/local/lib/clojure/deps.edn contains a few basic options that are applied to all projects. ...and that won't exist soon (it's being folded into tools.deps itself). In fact a version of the CLI tools was released that didn't install that, but a subsequent version put it back temporarily while tooling moves away from calling (clojure-env). Also, it isn't in that location on every system. Maybe less confusing to refer to the output of clj -Sdescribe for the locations of the files?

~/.clojure/deps.edn was created only after I ran clojure (I have a separate account for broadcasting so I can show things I have tried out on the other) and that makes sense to me as otherwise an installer would be putting that file in all user accounts. I would be very worried indeed if an installer were putting files in my user account, especially when running as sudo. If I was installing Clojure CLI tools into my own account I would still be surprised to see a config file appear outside of that install directory until I run the program.

Maybe there is a difference between running the Linux installer and running the homebrew install (I dont have Mac, so cant check)

I am covering clojure -Sdescribe and other options in the next blog post - hopefully finish tonight for the broadcast tomorrow. There doesn't seem to be much documentation about any of the operations available with clojure cli tools. I am just trying them out and seeing what they do. The --help option hints at what they do, but I havent seem details. So this is what the next post is about - giving examples of how to use the different options with the tool

Oh, that's interesting re: the user deps.edn -- I hadn't actually tested it, I just sort of assumed it was the installer that laid that down. So if you remove it and run clojure again, it puts it back? Good to know. Thanks.

I look forward to more blog posts then! 🙂

My latest one, exploring the mysteries of wha the command line options seem to do... (It's not as polished a post) http://jr0cket.co.uk/2019/07/gaining-confidence-with-Clojure-CLI-tools.html

reading...

From the ### Combining Aliases -- is there something missing there?

we have two aliases defined, `:We

congnitect spelling

Not sure what this means clojure will also include configuration from the test build configuration. -- does it need an example of clojure -A:test:runner in there?

The -Sdeps option will also add the given dependency to the current projects deps.edn

-Stree - adding dependencies to deps.edn

Hope that feedback is helpful!