This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-13
Channels
- # announcements (5)
- # babashka (35)
- # beginners (65)
- # braveandtrue (3)
- # calva (20)
- # cider (6)
- # clara (11)
- # cljs-dev (36)
- # cljsrn (64)
- # clojure (65)
- # clojure-europe (6)
- # clojure-germany (13)
- # clojure-italy (14)
- # clojure-nl (22)
- # clojure-spec (16)
- # clojure-sweden (6)
- # clojure-uk (81)
- # clojurescript (71)
- # conjure (120)
- # cursive (3)
- # datomic (10)
- # events (4)
- # figwheel (4)
- # figwheel-main (5)
- # fulcro (36)
- # ghostwheel (1)
- # graalvm (8)
- # helix (9)
- # jobs (4)
- # jobs-discuss (12)
- # kaocha (33)
- # leiningen (5)
- # luminus (1)
- # off-topic (24)
- # pathom (7)
- # rdf (4)
- # re-frame (3)
- # reagent (15)
- # reitit (11)
- # remote-jobs (1)
- # shadow-cljs (97)
- # slack-help (3)
- # spacemacs (23)
- # vim (15)
- # xtdb (35)
Conjure v3.1.0 is out! https://github.com/Olical/conjure/releases/tag/v3.1.0 a bunch of things added and fixed, enjoy!
Hey Olical, thanks! Conjure is really cool. I was trying it out a week ago and had a lot of fun. There are two main things from my workflow in fireplace that I couldn't figure out how to replicate though, I'm hoping you could help out.
The first is that I frequently uses cqc
which brings up a quick command line window. I tried using conjure's log buffer to put random one-off evaluations, but the log buffer isn't in the same namespace as my buffer, so there was enough friction there I couldn't figure out what to do.
The second thing I think is just a feature request, although if there's a way to extend conjure in my init.vim that would be great too. Fireplace has a cpr
command and I made a cps
command, which I use to run tests. Is there any way I could replicate this? Otherwise to run a test I have been putting (clojure.test/test-vars [#'the-test-function'])
and evaluating it.
So :ConjureEval (code-here...)
may well serve your needs although I appreciate that it isn't a buffer.
I normally just write it into the buffer in question (either in the file then deleted or a comment)
There's already test mappings that will run the test under your cursor, the namespace or the -test
variant of your namespace name (for testing while you evaluate the source)
<prefix>tc
will evaluate the current test under your cursor (anywhere in the form) for example. Where <prefix>
defaults to localleader.
i just started using https://github.com/liuchengxu/vim-which-key and i'm enjoying it!
i tend to create a lot of mappings that are organized by prefix, e.g. <leader>g
followed by another key to do git-related things, like <leader>gb
for :Gblame
(via fugitive) etc.
another example is <leader>b
for buffer-related commands (`<leader>bd` to delete the current buffer, etc.)
vim-which-key allows me to mindlessly type <leader>g
or <leader>b
and then wait half a second, and it shows me all of the mappings i have set up that begin with those two keys, so i can browse what sorts of things i can do and then pick the one i want
the big win here, in my mind, is that i often set up useful mappings and then completely forget about them. by putting them in front of my face on a regular basis, i can remind myself of what mappings i've made available and remember that i have them at my disposal
(if you've used spacemacs, this is a lot like what you get when you press the space key)