Fork me on GitHub
#vim
<
2019-12-12
>
martinklepsch10:12:14

@olical I've been looking into shadow+prepl again and was just wondering if it would be possible/make sense to write a small script that verifies some of the stuff you outlined in https://oli.me.uk/clojure-prepl-for-tool-authors/?

Olical10:12:18

Definitely possible yep, I've been meaning to I just don't have the time. A prepl compliance test suite would be awesome. Something I can probably do over Christmas unless someone beats me to it.

martinklepsch10:12:47

would be happy to contribute to this but not sure what the best setup would be. I'm thinking something fairly basic like a bash script but not sure what the requirements really are. If there were a setup somewhere with a single test that I could contribute to that would help me a lot

Olical11:12:07

I'll probably write a Clojure program for it, simple enough. I'll keep you posted and will share it in a few places when it's working. Again, unless you beat me to it 😛

Olical11:12:35

You give it a host and port, it connects and tries a bunch of things. Will require some timeouts too since you can lock up a shadow prepl fairly easily by throwing an error 😬

martinklepsch11:12:45

In my limited testing earlier throwing an error didn't lock up the prepl

martinklepsch11:12:51

but ¯\(ツ)

Olical11:12:47

Oooo interesting. Well, the testing tool will tell all I guess. Might write it over lunch at work if I have time

Olical11:12:49

Or start it anyway

Olical13:12:40

https://github.com/Olical/prepl-compliance-test I made a start, it tests :ret and :tap in a basic way but acts as a framework to easily add more.

Olical13:12:49

Was from an hour hacking over lunch so I only wrote those two tests but I got the framework down to write more easily.

dharrigan15:12:44

Anyone got any hints/tips for word boundaries in vim that know about Clojure? i.e., full stops, forward slashes etc...?

dharrigan15:12:19

i.e., if I delete a word, it deletes up to the word boundary

dominicm15:12:12

Which is built in

dominicm15:12:17

You don't need the plugin

Jan K15:12:49

Oh, I didn't realize it's built in now

dominicm15:12:45

It has been forever. I think its currently up to date too.

dominicm15:12:15

Maybe I'm misremembering

dave17:12:48

i still have it in my vimrc for some reason :thinking_face:

dave17:12:22

i did remove https://github.com/guns/vim-clojure-highlight a while back, and i remember that that adds some highlighting that isn't present out of the box, like highlighting core functions a different color, or something like that

dave17:12:39

ah, it says it right there in the repo description

dave17:12:47

it highlights referred and aliased vars

dave17:12:21

requires fireplace

dave17:12:40

coming back to vim-clojure-static, it isn't clear to me either how up to date the version of that that comes with vim is

dave17:12:38

it was last updated over 2 years ago, so i think there's a good chance that vim's is up to date now and there's no need for the plugin. at least, one would hope!

dave17:12:25

i'm removing vim-clojure-static from my vimrc as an experiment. i'll report back if i notice any issues

jahson19:12:39

I've noticed I use

Plug 'guns/vim-clojure-static', { 'branch': 'issue-77', 'for': 'clojure' }
but I forgot the reasons. Issue 77 is about performance.