Post went live! https://juxt.pro/blog/posts/vim-1.html 😟 First blog post, bit nervous. You guys wanna catch out my errors first? 😄

@dominicm having a read a now, will be sure to let you know! cheers

@dominicm I think the link to nvim-parinfer.js is incorrect. Currently seems to point back to the blog post.

@dominicm how often do you use refactoring tools when working with clojure?

@dominicm @jarrodctaylor same with the follow parinfer link in the same paragraph

@dominicm good quote from Case Nelson

Hrm, should I be using vim-sexp instead of paredit?

@jarrodctaylor @mikepjb Thanks for that! Fixed those links.

@mikepjb RE refactoring, not as often as I'd like. I have a rough idea of what's available though, and the rename-symbol stuff is just excellent.

I figure it will eventually become ingrained. Though, I probably have targetted the wrong ones for regular usage.

right

I regularly use crcn (Clean namespace) actually, so that's one that's ingrained pretty well.

I also think that magic require would be pretty cool to get setup.

Using neovim with set ft=clojure and call Parengage() or whatever to setup vim-sexp is pretty neat do you use this in your setup?

so you end up with a repl with paren balancing and syntax highlighting like emacs

What is Parengage()?

@jebberjeb I think vim-sexp is less... intrusive than paredit. Paredit breaks repeat (`.`) and changed dd in a way that didn't consistently balance.

paredit/vim-sexp but very much a WIP

https://github.com/michaelbruce/vim-parengage/commits/master

watching

the last commit adds paren balancing for nvim in terminal mode

That's pretty cool.

Is that your motivation for writing this?

I wanted a less buggy paredit

the nvim stuff just came about when trying boot/lein repl in terminal mode

which was as simple as copy pasting inoremaps to tnoremaps

heh. I would be interested to see a truly less buggy paredit.

haha I’m using vader.vim to unit test the movements

It'd be nice to have vim-sexp + dd that understood. That may be possible soon with the neovim api. But I don't want dd rebound, I want the TextChangedEvent to say "oh, this area is gone... ))))). Okay, we're good" And I think you need a shadow buffer for that. I might be wrong.

what’s a shadow buffer?

It's a way of keeping a replica of a buffer, to do transformations, there was also mention of gofmt.

https://github.com/neovim/neovim/issues/1114

Oh, so TextChanged is probably good enough for this?

Oh, except you don't have a delta.

I seem to say Oh a lot..

good enough for what?

vim-sexp + dd?

Doing a generic balance, instead of hardcoding dd

not sure I understand how the generic balance works

(defn serve-pdf
  "Takes an encrypted data string, requests a pdf from s3 and watermarks it. Outputs the pdf"
  [http-request]
  (println (str "Request for " (get http-request :uri))))

say your cursor in on the capital R in request on the last line

if you dd would the text become

(defn serve-pdf
  "Takes an encrypted data string, requests a pdf from s3 and watermarks it. Outputs the pdf"
  [http-request]
  )

Yeah. It would have to figure out which bit changed, and what is now unbalanced because of it.

The key part for me is that it wouldn't override dd though, just respond to the text changing. So that plugins which delete lines for me don't break (for example)

I don’t know if smart-parens is any better but there’s plenty of behaviour where paredit misbehaves - like pasting unbalanced text into your document

anyway it’s good to vimscript every once in a while!

Absolutely!

you can get the changed area froma textchanged event most of the time with registers. it's not perfect though.

> it's not perfect though For me, vimscript in a nutshell

@dominicm the acid link redirects to the blog post instead of acid repository

@ndrluis I thought I'd fixed that. Which section is the link in?

@dominicm “Future adventures” section

@ndrluis hmm, thought I'd fixed that section. I'll take a look.

@dominicm maybe an addition for the future adventures section: https://github.com/maitria/avi

@jebberjeb must admit, not decided which vim clone takes my interest currently. Kakoune looks good on it's own way. Neovim seems most committed to extensibility though.