Fork me on GitHub
#vim
<
2022-02-03
>
emilaasa06:02:22

Does anyone have a sample vim config that uses a lot of LSP features? Would be interesting to see other peoples bindings and so on.

walterl02:02:04

Not sure if it qualifies as "a lot", but most (all?) of my LSP usage is via coc.nvim: https://github.com/walterl/dotfiles/blob/master/_config/nvim/init.vim#L218-L238

nate17:02:52

Another example, mostly cobbled together from others in this channel (and #conjure): https://github.com/justone/dotfiles-personal/blob/personal/.vimrc#L536-L572

💪 1
uosl10:02:25

docstrings and jump-to-definition for both clojure.core and libraries work now. i think i had to build the project, then restart nvim and give clojure-lsp 1.5 minutes to finish analyzing the project (its progress was logged when i set neovim’s lsp debug logging.

Matt Butler11:02:25

Hey, long time fireplace user, I think its time I try something else, are there any good summaries of the differences between conjure and iced (both seem very good and feature rich)? Thanks 🙂

practicalli-john18:02:40

If you want to try something different, I suggest https://github.com/rafaeldelboni/nvim-fennel-lsp-conjure-as-clojure-ide It's an neovim config with conjure, Clojure LSP and a handful of other related plugins. It's comprehensive enough for Clojure development, but minimal enough to fairly easily understand and customise

🎉 4
👏 2
vim 2
❤️ 1
uosl11:02:51

i have never used conjure, but i switched from fireplace to iced some years ago, if you want a comparison between those

Matt Butler11:02:54

Perhaps, if theres anything you wish you could have told yourself before you switched?

uosl11:02:53

fireplace has received a lot of work since i moved away from it (particularly clojurists together funding) so what I say may no longer be true, but my main gripe with it was issues getting it to run for different clojure projects using different tooling, and having to add dependencies for it. with iced as long as you put add its bin folder to your path, it will work with all projects without having to mess with project.clj/deps.edn/etc

uosl11:02:35

i still miss the quasi-repl of fireplace. with iced you have to take a more emacs approach and make changes to the file for transient evals

Matt Butler11:02:41

I think I'm looking for a slightly more "do it for me" approach, maybe in exchange for some customisability. I tried to work out how I'd implement https://github.com/m00qek/baleia.nvim for fireplaces cqp or runtest and quickly ran into questions I didn't know the answer to, or even how I'd find the answer. Such as what buffer name of the preview window is.

Matt Butler12:02:35

Iced does seem more like that kind of project, but maybe I'm getting the wrong impression 🙂

uosl12:02:55

it’s definitely very “batteries included”

uosl12:02:43

with let g:iced_enable_default_key_mappings = v:true you’ll also get a complete set of bindings added to your leader

Matt Butler12:02:06

Might be a stupid question, but is attempting to remap the various commands to use the fireplace bindings a viable approach or better to bite the bullet just the iced ones?

uosl12:02:27

I think that would be viable, although there won’t be a 1:1 mapping of commands due to lacking the quasi-repl. if you :help iced you can see the default mappings at the bottom

Matt Butler12:02:52

Good point 🙂

Matt Butler12:02:06

Well thanks for the advice :thumbsup: much appreciated.

uosl12:02:15

Glad I could help!

practicalli-john18:02:40

If you want to try something different, I suggest https://github.com/rafaeldelboni/nvim-fennel-lsp-conjure-as-clojure-ide It's an neovim config with conjure, Clojure LSP and a handful of other related plugins. It's comprehensive enough for Clojure development, but minimal enough to fairly easily understand and customise

🎉 4
👏 2
vim 2
❤️ 1