This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-17
Channels
- # announcements (12)
- # babashka (27)
- # beginners (65)
- # biff (8)
- # calva (22)
- # clj-kondo (1)
- # clj-otel (5)
- # clojure (65)
- # clojure-europe (127)
- # clojure-nl (1)
- # clojure-norway (11)
- # clojure-portugal (2)
- # clojure-uk (2)
- # clojurescript (18)
- # cursive (5)
- # data-science (3)
- # datahike (14)
- # datascript (3)
- # datomic (7)
- # deps-new (11)
- # emacs (31)
- # exercism (1)
- # fulcro (1)
- # honeysql (3)
- # hyperfiddle (38)
- # introduce-yourself (4)
- # leiningen (2)
- # malli (20)
- # meander (2)
- # missionary (3)
- # off-topic (4)
- # pathom (3)
- # practicalli (2)
- # reagent (5)
- # releases (1)
- # sci (1)
- # shadow-cljs (9)
- # xtdb (8)
Hi there! Could you please recommend some tree explorer for emacs? Maybe there is some that can show clojure deps tree too 🙂
and the idea of showing clojure deps tree sounds pretty interesting, I may try to add that in lsp-treemacs in the future
Thank you Eric! Just installed it. Looks very nice. I don't understand, how I live in emacs without it:)
haha yea, one of the reasons I think today's framework are pretty nice like doom and spaceemacs, you find really useful stuff in there and can choose to enable or disable
Hi. What should be handling jar:file:/home/....jar!/com....
? It feels something is missing in my setup. I found no mentions in CIDER docs of some buddy package that does that handling. jarchive
adds a handler to find-file
only, but CIDER does browse-url
so even with that I'm not sure how people have it working :thinking_face:
Also the TRAMP-ish string would be jar:file:///home..
but CIDER yields jar:file:/path
jarchive was written with eglot in mind, not cider. Can you write out the steps to reproduce this (perhaps with a minimal repository to clone) so I can see what is going on with cider and the jar url?
it's a Doom Emacs setup (Clojure layer) with a simple new project with these requirements
:dependencies [[org.clojure/clojure "1.11.1"]
[com.slack.api/bolt "1.27.3"]
[com.slack.api/bolt-jetty "1.27.3"]]
and what I expected was that enrich-classpath
would lead to local documentation JAR's, which it does, albeit not unpacked
and so what I expected was that CIDER would either have some companion code that deals with that so the docs land on eww or something, or maybe Doom should have jarchive
in the Clojure layer and doesn't, but then the URL's don't match, as CIDER reports it in that style that doesn't quite fit
Sorry for really slow response. I think in this case I might be able to have jarchive work the URL format cider uses, jar:file:
. Currently jarchive is expecting jar:file://
Though I'm not sure what to do about cider using browse-url, I need to try it out
I'll see what I can do and report back here
^ that is for the the *cider-doc*
functionality on a Java package. C-c C-d C-d
on Class/staticMethod
yields com/...html
as the javadoc target, but doing it on Class
separated yields that jar:file
path
When you change your .dir-locals.el
how can you refresh it so cider-jack-in will pick up?
@U11BV7MTK that's not defined in my emacs
and before you jack in again and it takes forever, call c-h v [ret] <variable-name>
and confirm its value is what you are hoping before. so you can save the “jack in, didn’t work…” cycle that takes a while
If you have no unsaved changes you can also do M-x revert-buffer
which is the same as simply closing the buffer and reopening it.
.dir-locals.el
is only read when opening a buffer and won't be updated for any already opened buffers
So the buffer that is current when running the command must be opened (reverted) after any change to .dir-locals.el
Also use the universal argument before issuing the cider jack-in command to see the full details of the command to run in the mini buffer