I often do something like this when iterating on a piece of code:

I use nvim, conjure, lsp. How would I approach automating that action?

A couple of ideas would be: • a normal vim macro • maybe there's some API in Conjure?

I'd just use a normal vim binding, bound to a function.

if you've got vim-sexp which has various motions and text objects for s-exprs then something like this might work. Use it with the cursor on the name of the binding. It selects the first element moves to the end of the next, yanks them then pastes them into a command line using :ConjureEval. Clunky but works mostly. nmap <leader>cdl vie<m-e>y:ConjureEval (def <c-r>")<cr>

That's messing with the clipboard though, but yeah.

Cool I'll test something like that!

@U02EP7NKPAL That worked like a charm! Thank you! Now I feel a hacker in the movies

Thanks, guys, didn't even think about it, and it's really handy

@U02EP7NKPAL Very nice, I never knew I needed this! It also works with IcedEval for vim-iced.

This is slightly different but works for me

(nvim.set_keymap :n :<leader>cdl "vi]y:ConjureEval (def <c-r>\")<cr>" {:noremap true})

Oh god it works again! Thanks :D

That funky binding has become integral to how I work, pretty funny!

Does not work for multi line let tho

What’s an example of a multi line let? Vim-sexp motions should work fine across lines

(let [a 1 
      b 2])

I can't get the M-e binding to work in my fnl config

So this works on a let with one line, like (let [a 1]) (nvim.set_keymap :n :<leader>cdl "vi]y:ConjureEval (def <c-r>\")<cr>" {:noremap true})

But if I run it on the two line one, it will go until the ending ] and then get an error like this: ; eval (command): (def a :b b :c) ; (err) Syntax error compiling def at (src/analysis/core.clj:1:1). ; (err) Too many arguments to def

If I naively try and bind the same binding that worked great in vimscript, translated to this: (nvim.set_keymap :n :<leader>cdl "vie<m-e>y:ConjureEval (def <c-r>\")<cr>" {:noremap true})

I end up in visual mode - so I don't know if it's able to interpret the <m-e> string correctly

It still works correctly if I manually run the motions vie<m-e>y

I got the same issue, will have a play with it later

That vi] will select everything in square brackets, so every binding in the let which won't work if there is more than one.

Looks like it works if you set noremap to false (not really sure what difference that makes!)

(nvim.set_keymap :n :<leader>cdl "vie<m-e>y:ConjureEval (def <c-r>\")<cr>" {:noremap false})

Ah yes, of course. noremap means interpret the mapping as using default mappings (not any mapping that other plugins or you might have set). Usually that's what you want but in this case we do want to use a plugin's mappings so we need noremap=false. That's why the original mapping I posted used nmap, not nnoremap.

btw - an easy way to use vim script mappings in lua is to use vim.cmd to run vimscript, eg. vim.cmd[[ nmap <leader>cdl vie<m-e>y:ConjureEval (def <c-r>")<cr> ]]