Fork me on GitHub
#vim
<
2019-10-24
>
dave00:10:47

it isn't quite clear to me yet - are there advantages of vim-clap over vim-fzf? like, if i'm happy with vim-fzf, is there potentially any reason to switch to vim-clap?

dave00:10:04

so far, it seems like vim-clap might just be an alternative for people who can't / don't want to install fzf

walterl00:10:26

Heh. In the same way vim-fzf is an alternative for people who can't/don't want to install rg 😝

Aleksander11:10:58

does rg support fuzzy matching on any inputs? I thought they serve different purposes

walterl18:10:46

AFAIK rg is just (another) faster replacement for grep

dave00:10:09

windows users, etc.

dave00:10:54

hmm, the built-in commands do look pretty sweet. like, you could set that all up using vim-fzf, but with vim-clap you don't have to

dave01:10:02

i just gave vim-clap a try and it's super buggy out-of-the-box, from my perspective

dave01:10:16

i'll stick with vim-fzf, at least for now

dharrigan05:10:13

Super Buggy? Can you elaborate? I haven't experienced anything that appears to be buggy.

dave11:10:01

I didn't capture any of the error messages, but there were multiple of them at various times, just trying to do basic things

dharrigan12:10:57

Interesting. I'm not seeing any error messages when using vim-clap - i.e., searching, opening etc.. all appears to work as defined.

dave12:10:20

it could easily be something unusual about my setup. i'll give it another try at some point

dave12:10:18

i also got the "fzf window floating in the middle of the screen" configuration set up, and i'm really enjoying it. more than i thought i would 😄

dharrigan12:10:39

It's all good. I was wondering if I was missing something if you had errors and I did not 🙂

mynomoto13:10:17

I moved to vim-clap a couple of days ago and I'm really enjoying it. I got problems using it on git buffers where it gives strange error messages and took me a while to understand.

dominicm12:10:15

Btw, this week's clojurescript podcast is about vim (and I'm a guest!) https://clojurescriptpodcast.com

🎉 5
sogaiu18:10:27

thanks for doing this - quite informative. with all of the choices, was having a hard time deciding on what to focus on to get started. may be a tree diagram would be generally useful.

dominicm19:10:33

Fireplace / async-clj-omni / asyncomplete.nvim / vim-sexp I'd say that's a good starting stack.

dominicm20:10:04

(I've considered making a vim package out of all this, but not put the effort in)

dave12:10:51

awesome! i think you're the obvious choice in this series about setting up different editors for clj development, to do the one about vim. i'm looking forward to listening to it

dharrigan12:10:04

(neo)vim ftw! 🙂

dominicm12:10:06

I hope I did it justice, I didn't mention everything because voice is a difficult format

dominicm12:10:09

I think the best format is a tree diagram as you split at decision points

dave12:10:45

yeah, it's difficult when you have multiple parties trying to decide the direction the conversation should go, in real time

dominicm12:10:37

I actually found the hardest part to be the mass amount of choice, and deciding when you'd choose one over the other.

💯 1
dominicm12:10:03

It's a really subtle conversation that has to happen per plugin. I'm not sure I understand all of the subtleties for all cases either.

Aleksander11:10:06

writing down those subtleties, decision points and sets of compatible sets of plugins would be very useful ducks and runs away!

Aleksander11:10:05

or even encoding it eg inside spacevim clojure layer

dominicm13:10:25

The problem is that it would be an encoding of preference, tolerance and familiarity with clojure/vim

dominicm14:10:22

Good at vim, bad at clojure is different than good at clojure bad at vim for the plugin set. Peak performance vim is different than mostly productive with modal editing today vim.

dave12:10:41

oh yeah, so vim is interesting because we basically don't have a go-to framework

dave12:10:07

there is a massive amount of plugins, all maintained by different people, mostly in isolation

dominicm12:10:20

I think vim users can be divided into 2 groups largely: - those that like the minimalism - those that ... ??? I'm not sure. This group doesn't seem to mind taking on new things. If you like minimalism, you're gonna tell ALE to shove it and use makeprg. If you're in the latter group, you're willing to use ALE. I think it's a scale between these two groups though.

dominicm12:10:33

I can't stand ALE, it's too much.

dominicm12:10:13

I love fireplace because it fits into vim very naturally (as most tpope plugins do)

dominicm15:10:43

Just looked in on neomake, I don't know why this isn't more popular, adding clojure support was easy (although someone could contribute it!). I wish it had compiler support (there's an open issue) but that's okay.

dominicm15:10:12

One annoyance, I can't disable the location list stuff. That's very frustrating when combined with automake 😞

dave15:10:57

I used to use neomake and then switched to ALE about a year ago. I don't remember why I switched. I don't remember anything particularly wrong with Neomake. I'd be curious to know how you compare the two, @dominicm

dominicm15:10:29

One has a language server client in, and one doesn't.

dominicm15:10:33

Something about ALE feels like having a tree attached to a car. It's probably useful to someone, but not me.

dave16:10:21

It does bother me that I find myself using 2 plugins (ALE and COC) that are both LSP clients

walterl16:10:51

omg, this! I also use both, and I have that same constant niggling feeling.

dave16:10:30

Something doesn't add up there!

dominicm16:10:15

I saw a comment suggesting that it's okay, you don't take any bulk for the pieces you don't use. But I know what my software is like when it does too much, so I don't want that in my editor.

dave16:10:20

Yeah, same. It just feels more complex than it should be.

dominicm16:10:02

I like compiler & makeprg a lot. But I can't figure out how to run multiple.

dominicm16:10:26

I'm sure there's a quickfix virtual text around which would make the feature fairly redundant (that might be how neomake does it tbh, which would explain why I can't disable the lists)

dharrigan16:10:26

Yeah, I use ALE and CoC too and haven't qot round to figuring it out all yet

walterl16:10:08

On the makeprg-to-ALE scale, I'm definitely on the ALE side of things (I think a more concrete measure is LOC in $MYVIMRC 😜), but what I would really prefer is to have CIDER nREPL do all the Clojure things, and bring it into vim via fireplace. No vim-only stuff that reinvent existing CIDER functionality. Like vim-cider does, just... more/all of it 😛.

walterl16:10:27

Hopefully I can pinch off some time somewhere to get that going.

dominicm16:10:50

vim-cider actually does that too, it uses the cider-nrepl middleware.

walterl16:10:58

Awesome. Maybe I should focus on helping with that...

dominicm16:10:29

It's languished a little lately, I'd appreciate a hand 🙂