It might be that it can't be done, fully. They are called Overview Rulers. Maybe that can help in your googling. Or just in the settings search.

Thanks, that may help in finding a solution

In my favorite theme, it's not even neutral grey. It's hot pink, bright yellow, sky blue. Looks like we will hopefully be able to turn it off in the near future.

The language is surprisingly (and by design) quite stable. the book should be fine. I'd ignore anything lein related and read the https://clojure.org/guides/deps_and_cli and use that for starting projects and build related things.

Okay, thanks. Why should I ignore anything lein related though?

I use lein for my projects still

This is an informative thread on the topic: https://clojureverse.org/t/is-there-a-sales-pitch-for-switching-to-deps-edn-from-lein-in-2020/5367

The deps.edn ecosystem has improved greatly since then too. For example, tools.build handles a lot of the complaints or sharp edges in that thread, and community members have written more libraries to smooth over existing issues.

The thing that sticks out the most of being "out-of-date" in Clojure Applied is that it reaches for records first over maps early on in the book. I think conventional wisdom these days is to reach for maps unless you have a good reason to use records. Some of the lib recommendations have seem to fallen out of favor for newer alternatives as well, especially libs that are more data-oriented, which the book doesn't cover.

I would agree with most of the above, although lein is still the most widely-used build tool for Clojure, so it's perfectly reasonable to stick with it for now even though deps.edn is likely to be the future. I'll personally toss in a recommendation for Joy of Clojure as a next book -- it goes deeper than most books IMO and is a great help for the shift from "learning Clojure" to "real expertise in Clojure" if that's the transition you're working toward. It's 2014, but as @U11BV7MTK points out, Clojure is a very stable language.

@UBHTL6AF3: I think what u said seems to be my impression too. The first chapter of the book was an interesting read with the recommendation about usage of records for domain-modelling but then I remembered something which Rich Hickey said "Just use maps" and I also felt conflicted with records, but I understand the rationale. My qualms also were about the usage of libraries and how up-to-date they still are and I wad hoping for a newer updated release of that book.

@U077BEWNQ: I think I have learned enough clojure by reading brave and true + getting clojure and I was specifically looking for a book on application of clojure with best practices which is why I chose Clojure Applied. How is Joy of Clojure different from Brave and True/Getting Clojure?

I've only skimmed Getting Clojure, but JoC goes much, much deeper than Brave and True, to the point where I usually don't recommend it as a first book for most people, because it's quite dense. The table of contents http://www.joyofclojure.com/toc/ links to several sample chapters if you'd like to take a look in order to get a sense.

Ah, and the table of contents https://www.manning.com/books/the-joy-of-clojure-second-edition expands so you can see the detailed contents, which will give you a decent idea of the depth.

Switched to Joy of Clojure it really is a joy to read it! Thanks everyone!