Clojurians Log v2
emacs 2026-06-05
bit of a weird issue this morning which I'm sure is something funky about my setup, but would appreciate help debugging this. On my current project we're using clojure-indent-style 'always-indent, so
(assoc m
:foo bar)(assoc m
:foo bar).dir-locals.el and that's getting picked up
clojure-indent-style is a variable defined in ‘clojure-mode.el’.
Its value is ‘always-indent’
Original value was ‘always-align’clojure-mode (and cider) through straight, and it stopped working, it's aligning as though it's set to always-align. So I downgraded both (checked git reflog for what I was on previously), restarted emacs, but it's still aligning rather than indenting.
version I was on (and reverted back to) for clojure-mode: 28dc021
version I tried to upgrade to: c3b039edug into clojure-indent-function and seems to easiest fix is to set clojure-enable-indent-specs to nil
Seems Orchard removed the orchard.java/*analyze-sources* dynamic var, which is breaking haystack...
I can make a PR, but should I remove haystack's usage, or bring back the var? given that this is a public var perhaps removing it was unwise and it should be brought back?
Haystack is kinda deprecated, but it depends what you need to do with it
Some functionality has been transferred to orchard.stacktrace
But parsing stacktraces from text is not there, you still need haystack for that. If so, your best bet would probably be a PR to haystack that adapts to latest orchard
I just need (stack/analyze throwable)
> perhaps removing it was unwise > No offense taken, but a patronizing tone is not necessary and rarely leads to productive outcomes.
If throwable is a Throwable object, then orchard.stacktracw/analyze (don't remember exact function name, on the phone right now) will fill that
And you can thus drop Haystack altogether
perfect! thanks for pointing out that haystack has mostly been replaced by orchard, I was not aware of that
Sorry, wrong namespace
in that case maybe the most helpful thing is I send a PR to put a message at the top of the haystack README pointing at orchard/stacktrace? or do you prefer I just leave it alone?
I don't object updating the Haystack README at all like you suggest. The reason we didn't hard-deprecate it is that the text-parsing functionality is still only there, and somebody might still theoretically want that, but as you yourself discovered, that person would have to dig through some broken compat to get that functionality working.
And sorry for lashing out a bit, my usual grumpy self showing 🙄
no worries Oleksandr, I've been there myself, and I probably could have phrased that better. Thanks for your help, I'll try to put something in the README for the next person.