This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-12
Channels
- # announcements (2)
- # beginners (36)
- # boot (6)
- # calva (2)
- # cider (18)
- # clj-kondo (1)
- # cljdoc (2)
- # cljs-dev (2)
- # clojure (130)
- # clojure-boston (1)
- # clojure-brasil (3)
- # clojure-czech (1)
- # clojure-europe (11)
- # clojure-italy (4)
- # clojure-losangeles (37)
- # clojure-nl (9)
- # clojure-seattle (2)
- # clojure-sweden (8)
- # clojure-uk (23)
- # clojurescript (13)
- # core-async (21)
- # cursive (13)
- # data-science (6)
- # datomic (12)
- # emacs (36)
- # figwheel-main (9)
- # fulcro (76)
- # juxt (2)
- # keechma (18)
- # leiningen (4)
- # off-topic (13)
- # pedestal (37)
- # re-frame (21)
- # reitit (2)
- # shadow-cljs (78)
- # spacemacs (23)
- # sql (13)
- # tools-deps (25)
- # uncomplicate (4)
- # unrepl (1)
- # vim (27)
I think there are a number of ways but my experience was that vim-iced had a good OOB setup https://github.com/liquidz/vim-iced https://twitter.com/uochan/status/1034404572368842752
I didn't realise that had debugger support now.
I was trying out acid.nvim, but couldn't figure out how to get started: https://clojureverse.org/t/getting-started-with-acid-nvim-and-leiningen/4527 Has anyone had any prior experience with it (on the new 2.x version)?
seems like one can start a socket repl via project.clj
: https://stackoverflow.com/questions/34926360/how-can-i-start-a-socket-repl-in-clojure-1-8-from-leiningen-or-boot
although that is different from what is mentioned at: https://oli.me.uk/2019-03-22-clojure-socket-prepl-cookbook/
Yep, you can do although I haven't tried. You just need to start a socket prepl. The example where I start it from within Clojure (rather than from the command line arguments) should work for you!
or do i have to add additional information inside a .conjure.edn
in my leiningen project directory?
Yep, you'll need to create a conjure.edn (the . is optional, depends on other config files in the same dir and your preference) with the chosen port inside it.
You can also select a port at random, write that to a file and load that into your conjure.edn with the #slurp-edn
reader macro. If that floats your boat.
That's mainly for when you're using something like a plugin in boot or lein to start your prepl though where it'll pick a port for you and write it to a file.
More fluid "installation to productive" user guides will exist at some point. I'm still churning away with internal things and features though, docs etc are one of the last things in my 1.0.0 plan right now because then it'll require a lot less re-writing. All of the info should be in the readme right now, it's just hard to parse all at once.
I'm also doing other side project stuff and moving this month so time has been... limited.