@dave Hadn't seen it, checked it, but it doesn't seem to give anything extra to my workflows, unless I start using :terminal for other things than the repl. Most likely I want to either send sexps (which the line based selection doesn't help) or have an interactive session with tab-completion, command history and so on, so I don't want to input commands via the :T

Is there a reasonable way to get the current namespace of the file, for running (run-tests 'your.namespace 'some.other.namespace) in the repl?

*ns* has the current namespace

It's the current namespace in the repl, but that's different from what file you are in

fireplace has a regex it uses.

I think the fn is safe to just copy.

function! SendToTerm(lines)
  call jobsend(g:last_term_job_id, add(a:lines, ''))
endfunction

function! SyncRepl()
  call SendToREPL("(require '[clojure.pprint :refer [pprint]])(require '[clojure.repl :refer :all]) #_(require '[hara.reflect :refer :all]) #_(require '[hara.class :refer :all])")
  call SendToTerm([" (in-ns '" . fireplace#ns() . ") "])
endfunction
function! SendToREPL(sexp)
  call fireplace#session_eval(a:sexp)
endfunction

@tomi.hukkalainen_slac Curious to see where you end up w/ it. I usually just move to the top of the buffer, eval the ns form to switch namespace, then just run-tests, w/ no args.

fireplace#ns() is at https://github.com/tpope/vim-fireplace/blob/265fc95f7b1b3ec4371403a2f9074dc171bf7978/plugin/fireplace.vim#L574

Oh my, vimscript 😞

😞 I know

I’d been trying to avoid it.

And I'm one of those people who can't just stop at "it works" but has to go to "I understand it"

So I'm immediately stopping at things like "What's that a:0, the first argument?" and "is the s: in s:buf just a naming convention, or does it somehow change how the function works"

But I'll try to just copy paste enough to get it working, and leave it at that 😉

Or…

Make a keybinding that goes to the top of the file and eval’s the first form, which is almost always going to be the ns form.

I wonder if that requires less vimscript

I mean learning less

I think you’d do that with :norm, so yeah probably.

I saw a post in Planet Clojure today, with some statistics about clojure developers. I don't know what the target group really was, but I was quite surprised that vim was listed above 10% in IDEs/editors.

Maybe clojure is different from older lisps, or I'm just pessimistic since noone else around me uses vim 🙂

We have some users here at JUXT

I find that a lot of newcomers to Clojure from languages like Ruby & Python are vimmers. It used to have a higher marketshare, but I think Cursive eroded it a good bit over the last few years.

Spacemacs is the virus I see