This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-04
Channels
- # beginners (90)
- # boot (5)
- # cider (89)
- # cljsrn (27)
- # clojure (33)
- # clojure-dev (2)
- # clojure-italy (3)
- # clojure-spec (35)
- # clojure-uk (17)
- # clojurescript (93)
- # code-reviews (1)
- # datascript (2)
- # datomic (14)
- # defnpodcast (6)
- # emacs (11)
- # figwheel (8)
- # figwheel-main (6)
- # hyperfiddle (14)
- # jobs-rus (1)
- # nrepl (3)
- # off-topic (13)
- # onyx (6)
- # reagent (6)
- # reitit (4)
- # shadow-cljs (110)
- # spacemacs (1)
- # tools-deps (10)
- # vim (17)
@thiru0130 here’s how I do it w/ only Neovim terminal and a bit of Vimscript https://medium.com/@jebberjeb/vim-clojure-tooling-redux-16ce62e4d727
thanks @jebberjeb
I read your posts on this a few weeks or months ago. It sounds interesting but I felt it was missing some niceties from vim-fireplace like omni complete
But this is all you use when writing Clojure? I suppose it works equally well with Clojurescript
I'm sympathetic to a lot of your points in those articles.. vimscript, nrepl, piggieback are all just overly complex..
Well, the stuff in that article - that hasn’t been collected into a plugin. I did another plugin that’s similar but it relied on the Neovim remote API + SocketREPL.
I should probably just make a simple plugin from the Vimscript in that last article at some point.
So are you using what you outlined in that most recent article or what you currently have in the plugin?
@thiru0130 I’m using the stuff in that medium article. I think my .vimrc is up to date with it all https://github.com/jebberjeb/dotfiles/blob/master/.vimrc