Fork me on GitHub
#vim
<
2018-05-12
>
dominicm08:05:12

I was looking at apathy and thinking it would be cool if 'path' could be set to the jvm classpath. Turns out it's not so easy, the way zipfile reading is implemented means that it doesn't work.

dominicm09:05:58

https://github.com/vim/vim/issues/2902 opened this 🙂 If I'm shut down / get tired of waiting, I'll try going to neovim directly.

dominicm09:05:05

Being able to gf on data_readers.clj or foo.css from a clojure file would be really nice.

dominicm09:05:18

But also :2find data_readers.clj and so on

niclasnilsson14:05:12

Anyone knows why https://clojurians-log.clojureverse.org/vim doesn’t have logs after 2018-04-17?

dominicm14:05:01

That's annoying

dominicm14:05:13

#community-development might know

niclasnilsson15:05:00

Ok, I’ll ask there

niclasnilsson15:05:43

Very annoying, since there are so many good things floating around in here that doesn’t seem to be possible to go back to.

niclasnilsson15:05:29

Looked at others, and it’s seems to be many/all channels that are not logged

dominicm16:05:13

After much turmoil, I just got my first refactor.nvim command to run with node-host party-corgi

parrot 8
🎉 4
dominicm17:05:47

Hopefully we can stop pinning a specific sha soon 🙂

dominicm18:05:59

Everything appears to be working

dominicm19:05:42

Hi @renewdoit 👋 I've been looking at your fun-map library today, looks very cool 🙂

renewdoit19:05:57

I use spacemacs now, but look for vim to replace it.

renewdoit19:05:37

Is there up-to-date article to read for newbie like me?

dominicm19:05:56

https://juxt.pro/blog/posts/vim-1.html only slightly dated, also authored by me 🙂

dominicm19:05:11

I'd recommend throwing in something like https://github.com/SevereOverfl0w/vim-replant now too

renewdoit19:05:31

cool, thanks, I am going to read it now.

dominicm19:05:58

https://github.com/SevereOverfl0w/clj-refactor.nvim works with master node-client. I asked for a release, but none has happened yet. I asked here: https://github.com/neovim/node-client/issues/64 and you can "work around" it for now by cloning node-client and doing npm run build && sudo npm link

dominicm19:05:03

@eraserhd I noticed it doesn't play too nicely with Parinfer. I'm thinking about adding some hooks for disabling/enabling parinfer around modifications, but I figured I'd reach out and see if you had any ideas about how I could make the changes so it wasn't a problem.